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/bmachek/social-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/bmachek/social-mcp/instagram-mcp)<a href="https://agentmods.dev/mcp/bmachek/social-mcp/instagram-mcp"><img src="https://agentmods.dev/badge/mcp/bmachek/social-mcp/instagram-mcp/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/bmachek/social-mcp/instagram-mcp"><img src="https://agentmods.dev/badge/mcp/bmachek/social-mcp/instagram-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
instagram-mcp 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 8 lines scan A eb3bfae6ef81
instagram-mcp is an MCP server published in the GitHub repository bmachek/social-mcp (0 stars, last pushed 1mo ago), licensed GPL-3.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. 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
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.
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.
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.
viberoom
MCP server "viberoom" as configured in RatulMaharaj/viberoom. Runs locally from the viberoom Python package.
postforme-mcp-pro
Publish, schedule and analyze social posts across 9 platforms via the Post for Me API. Runs locally from the postforme-mcp-pro npm package. Needs 2 environment variables to run.
facebook-mcp
Facebook Pages MCP server for the Meta Graph API — publishing, insights, moderation, messaging. Runs locally from the @ivanbaev/facebook-mcp npm package. Needs 23 environment variables to run.