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/IvanBBaev/instagram-mcpWrote 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/ivanbbaev/instagram-mcp/instagram-mcp-ai)<a href="https://agentmods.dev/mcp/ivanbbaev/instagram-mcp/instagram-mcp-ai"><img src="https://agentmods.dev/badge/mcp/ivanbbaev/instagram-mcp/instagram-mcp-ai.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
instagram-mcp-ai 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 7d 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.
What it actually says
{
"instagram-mcp-ai": {
"command": "npx",
"args": [
"-y",
"instagram-mcp-ai"
],
"env": {
"IG_ACCESS_TOKEN": "",
"IG_ACCOUNT_ID": "",
"IG_APP_ID": "",
"IG_APP_SECRET": ""
}
}
}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.
- 7d ago First seen · 15 lines scan A 1f7066ea7c6e
instagram-mcp-ai is an MCP server published in the GitHub repository IvanBBaev/instagram-mcp (0 stars, last pushed 11d ago), licensed MIT. 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
instagram-mcp
Model Context Protocol server for the Instagram Graph API (Business/Creator accounts). Runs locally from the instagram-mcp Python package.
meta
MCP server for Instagram Graph API, Threads API & Meta platform management. Runs locally from the @mikusnuz/meta-mcp npm package. Needs 6 environment variables to run.
Public Instagram profiles and post feeds by handle, with hashtags and mentions parsed. Runs locally from the @hasdata/instagram-mcp npm package. Needs 1 environment variable to run.
instagram-mcp
Official Instagram Graph API MCP. Multi-account read, publish, comments, analytics + (review-gated) DMs for Instagram Business/Creator accounts. ToS-safe, no private API. Runs locally from the adelaidasofia-instagram-mcp Python package. Needs 2 environment variables to run.
video-analyzer
MCP server "video-analyzer" as configured in guimatheus92/social-knowledge-base. Runs C:/Users/guilh/repos/mcp-video-analyzer/dist/index.js with node. Needs 5 environment variables to run.
mcp-instagram
MCP server for Instagram. Runs locally from the mcp-instagram npm package.