Is the AgentStatus MCP Index down?

mcp-registry/io.github.carmel-labs-inc/mcp-index · registry v1.0.0 · server reports vsite-mcp-2

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 20:44 UTC · handshake 519ms

As of 2026-11-22 20:44 UTC, the AgentStatus MCP Index is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 10 minutes.

uptime (30d checks)
99.9%
checks observed
917
outages (90d)
1
tools
12

Live public MCP Index. Search, recommend, and call healthy MCP servers.

Point your MCP client at this streamable-http endpoint: https://index.mcp.agentstatus.dev/mcp

Agent-readiness: A (94/100)

A (94/100): 0 error(s), 1 warning(s) across 9 tool(s); ~1,678 tokens of tool definitions.
Scores higher than 70% of 27,663 MCP servers Glimind has audited.
Its tool list costs an agent ~1,678 tokens per session — lighter than 55% of servers.
94 → 94 since 2026-11-16
no tool-poisoning patterns
Descriptions100
Safety hints63
Schemas100
Protocol100
Stability100
Token cost100
Reliability100
Client compatibility100

What to fix (2)

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 →

Tools: send_feedback

1 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 →

Tools: send_feedback

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.carmel-labs-inc%2Fmcp-index/fixes

send_feedback 1 change
{
  "name": "send_feedback",
  "description": "Tell the developer this result was wrong or confusing. Call this after a tool, not instead of the tool.",
  "inputSchema": {
    "type": "object",
    "required": [
      "feedback",
      "tool"
    ],
    "properties": {
      "tool": {
        "type": "string",
        "description": "The tool you just called."
      },
      "context": {
        "type": "string",
        "description": "Why you are calling this tool, in 15 to 25 words, third person. Say what the user is trying to do."
      },
      "feedback": {
        "type": "string",
        "description": "What was wrong or confusing about the result."
      },
      "arguments": {
        "type": "object",
        "description": "The arguments you sent to that tool."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

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/io.github.carmel-labs-inc/mcp-index"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.carmel-labs-inc/mcp-index"}) over MCP.

Passed

Largest tool definitions

Static 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.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fio.github.carmel-labs-inc%2Fmcp-index.svg)](https://glimind.com/server/mcp-registry%2Fio.github.carmel-labs-inc%2Fmcp-index?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.carmel-labs-inc%2Fmcp-index?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.github.carmel-labs-inc%2Fmcp-index.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:9c5328f6974e7346…, first seen 2026-11-16, included at leaf 292645 of 385,173. Version history · verify what your client received.

Tools (12)

Compare: most reliable other servers · most reliable devops servers · most reliable retrieval servers · most reliable search servers · most reliable communication servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the AgentStatus MCP Index down right now?

As of 2026-11-22 20:44 UTC, the AgentStatus MCP Index is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 10 minutes.

How many tools does AgentStatus MCP Index provide?

AgentStatus MCP Index advertises 12 tools, including call_indexed_tool, call_server_tools, compare_records, finish_work, get_record.

How do I install AgentStatus MCP Index?

Point your MCP client at this streamable-http endpoint: https://index.mcp.agentstatus.dev/mcp

Is the AgentStatus MCP Index safe to connect to an AI 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.

Operator of AgentStatus MCP Index?

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.

Feedback
Help us improve