Home / MCP registry index / io.github.mcp-dir/instagram-mcp
io.github.mcp-dir/instagram-mcp in the official MCP registry.
Endpoint https://api.mcp.ai/p_instagram. Source: github.com/mcp-dir/instagram-mcp.
The registry describes it as: Instagram for AI agents: publish, read comments and DMs, insights, and engage from your account.
We could not reach this server's endpoint on 2026-10-29. Nothing was checked.
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read: 
[](https://lazaretto.dev/mcp-registry/io-github-mcp-dir-instagram-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.
Related
| BAMF.ai ai.bamf/bamf | 153 tools, nothing matched 2026-11-04 |
| SocialSeal com.socialseal/mcp | 119 tools, nothing matched 2026-10-28 |
| X Twitter com.jojapi/x-twitter | 107 tools, nothing matched 2026-10-27 |
| Synoptic com.synoptic/synoptic | 70 tools, nothing matched 2026-10-27 |
| DataCrazy io.github.mcp-dir/datacrazy-mcp | 70 tools, nothing matched 2026-11-05 |
| Flux LinkedIn MCP app.fluxgraph/linkedin | 67 tools, nothing matched 2026-11-02 |