Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/ishan-parihar/instagram-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/ishan-parihar/instagram-mcp-server/greptile)<a href="https://agentmods.dev/mcp/ishan-parihar/instagram-mcp-server/greptile"><img src="https://agentmods.dev/badge/mcp/ishan-parihar/instagram-mcp-server/greptile/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/ishan-parihar/instagram-mcp-server/greptile"><img src="https://agentmods.dev/badge/mcp/ishan-parihar/instagram-mcp-server/greptile.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
greptile scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to greptile — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"greptile": {
"type": "http",
"url": "https://api.greptile.com/mcp",
"headers": {
"Authorization": "Bearer ${GREPTILE_API_KEY}"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 9 lines scan A 482a81ff0bb2
greptile is an MCP server published in the GitHub repository ishan-parihar/instagram-mcp-server (1 stars, last pushed 3mo ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. It is 100% identical to greptile, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
performance_profiler
MCP server "performanceprofiler" as configured in probelabs/visor. Runs ./tools/performance-analyzer.js with node. Needs 2 environment variables to run.
security_scanner
MCP server "securityscanner" as configured in probelabs/visor. Runs ./mcp/security.js with node. Needs 2 environment variables to run.
dependency_checker
Check for outdated, incorrect, and unused dependencies. Runs locally from the npm-check npm package. Needs 1 environment variable to run.
openpost
Manage social publishing workflows through OpenPost. Remote server at app.openpost.social.
sociona-mcp-server
MCP server for Sociona social media API - interact with social media platforms through AI assistants and MCP-compatible tools. Runs locally from the sociona-mcp-server npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.