mcp-registry/co.civai.nova/instagram-web-agent · v1.0.0
As of 2026-10-26 20:21 UTC, the Civai Nova Instagram Web Agent MCP server is up with a Glimind reliability score of 70/100 (grade C). Over the last 30 days it answered 98.6% of Glimind's liveness checks. It had 68 outages in 90 days, with a median recovery of 7 minutes.
I use your Instagram Web browser session (Integrations → Instagram Web) via instagrapi, not Meta /…
Point your MCP client at this streamable-http endpoint: https://nova.civai.co/mcp/agents/instagram-web-agent
9 of 9 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
8 parameter(s) across 8 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Reachable 98.6% of the time over the last 30 days; median recovery 7 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 8 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fco.civai.nova%2Finstagram-web-agent/fixes
{
"name": "fetch_hashtag_recent_posts",
"description": "Instagram Web: fetch hashtag recent posts",
"inputSchema": {
"type": "object",
"properties": {
"detail": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "fetch_post_comments",
"description": "Instagram Web: fetch post comments",
"inputSchema": {
"type": "object",
"properties": {
"detail": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "fetch_user_recent_posts",
"description": "Instagram Web: fetch user recent posts",
"inputSchema": {
"type": "object",
"properties": {
"detail": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/co.civai.nova/instagram-web-agent"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/co.civai.nova/instagram-web-agent"}) over MCP.
converse ~70 tokensfetch_hashtag_recent_posts ~47 tokenssearch_instagram_accounts ~47 tokensfetch_user_recent_posts ~46 tokenslookup_instagram_profile ~46 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fco.civai.nova%2Finstagram-web-agent?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fco.civai.nova%2Finstagram-web-agent?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fco.civai.nova%2Finstagram-web-agent.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fco.civai.nova%2Finstagram-web-agent.svg :target: https://glimind.com/server/mcp-registry%2Fco.civai.nova%2Finstagram-web-agent?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:8ec8252b82aad41a…, first seen 2026-10-17, included at leaf 13510 of 75,268. Version history · verify what your client received.
Compare: most reliable other servers · most reliable retrieval servers · most reliable communication servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 20:21 UTC, the Civai Nova Instagram Web Agent MCP server is up with a Glimind reliability score of 70/100 (grade C). Over the last 30 days it answered 98.6% of Glimind's liveness checks. It had 68 outages in 90 days, with a median recovery of 7 minutes.
Civai Nova Instagram Web Agent MCP server advertises 9 tools, including converse, fetch_hashtag_recent_posts, fetch_post_comments, fetch_user_recent_posts, fetch_user_stories.
Point your MCP client at this streamable-http endpoint: https://nova.civai.co/mcp/agents/instagram-web-agent
Glimind scanned all 9 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.