Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AgentStatus MCP Index

REMOTE · INDEX.MCP.AGENTSTATUS.DEV

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

70 Trust /100

Last scanned (20 minutes ago)

Scores higher than 55% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 518 tokens (~86/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1
    • Tool “recommend_records” rewrote its description, which is the text the model reads security
  • 1 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 31 Oct 26 68

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://index.mcp.agentstatus.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.mcp.agentstatus.dev CN=YR1,O=Let's Encrypt,C=US 15 Oct 2026 13 Jan 2027 RSA 2048 SHA256-RSA 52085e5372982c596bd9894f64eeb4b6dc7
SANs: *.mcp.agentstatus.dev
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC bogus

Validation of index.mcp.agentstatus.dev. — Bogus

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
agentstatus.dev. present 32850 13 Verified
index.mcp.agentstatus.dev. Bogus address RRset signature failed verification
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://index.mcp.agentstatus.dev/mcp Verified 200
http (plaintext) http://index.mcp.agentstatus.dev/mcp Served over HTTP 200
MCP tools · 6 exposed · ~518 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
call_indexed_tool ~100

Run a tool on a public MCP server from the full AgentStatus Index. This connection does not list those servers. Call search_records or recommend_records first, then pass that slug and tool. The call is sent to that server and its result is returned here.

NameTypeReqDescription
argumentsobject–Arguments for that tool.
slugstringyesIndex slug, such as trip-logistics.
toolstringyesTool name on that server.

Structured output declared, but exposes no named fields.

No examples provided.

compare_records ~51

Compare two to five directory items by id, slug, or exact name. Returns stored details and the fields that differ.

NameTypeReqDescription
recordsarrayyesTwo to five record ids, slugs, or exact titles.
NameTypeReqDescription
differencesarray––
missingarray––
recordsarray––

No examples provided.

get_record ~37

Look up one directory item by id, slug, or exact name.

NameTypeReqDescription
idstringyesRecord id, slug, or exact title.
NameTypeReqDescription
recordobject––

No examples provided.

list_sections ~19

Show the sections in MCP for AgentStatus MCP Index.

Input schema present but exposes no named parameters.

NameTypeReqDescription
sectionsarray––

No examples provided.

recommend_records ~130

Return public MCP servers from the full Index for a need. Each match includes a slug and tool names. This tool only reads the Index.

NameTypeReqDescription
hoststring–Optional product host, same as search_records: cursor, copilot, vscode.
limitinteger–How many recommendations to return. Default 5, maximum 10.
needstringyesWhat the agent is looking for.
sectionstring–Optional section or partial section name.
statusstring–Exact facts.status value from this directory: operational, degraded, down, auth_required, unrated.
NameTypeReqDescription
criteriaobject––
recommendationsarray––
recordsarray––
totalinteger––

No examples provided.

search_records ~181

Search the full public MCP Index. The tools on this connection are only the Index, not the catalog. Pass the job as query. Optional host is cursor, copilot, or vscode. Each match includes a slug and tool names. Run one with call_indexed_tool.

NameTypeReqDescription
hoststring–Optional product host, same as the public Index query: cursor, copilot, vscode.
limitinteger–How many matches to return. Default 20, maximum 50.
offsetinteger–How many matches to skip.
querystring–Words an agent would type. Empty returns the directory in stored order.
sectionstring–Section name from list_sections. Partial names match.
statusstring–Exact facts.status value from this directory: operational, degraded, down, auth_required, unrated.
NameTypeReqDescription
limitinteger––
offsetinteger––
recordsarray––
totalinteger––

No examples provided.

Install

How do I install the AgentStatus MCP Index server?

AgentStatus MCP Index is a hosted endpoint at https://index.mcp.agentstatus.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · index.mcp.agentstatus.dev

# add to Claude Code
claude mcp add --transport http carmel-labs-inc-mcp-index 'https://index.mcp.agentstatus.dev/mcp'
Common questions

What is the AgentStatus MCP Index server?

AgentStatus MCP Index is listed in the public MCP registry as io.github.Carmel-Labs-Inc/mcp-index. Live public MCP Index. Search, recommend, and call healthy MCP servers. This page covers its hosted endpoint (https://index.mcp.agentstatus.dev/mcp).

Is the AgentStatus MCP Index server safe to use?

AgentStatus MCP Index scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the AgentStatus MCP Index server expose?

AgentStatus MCP Index exposes 6 tools: search_records, get_record, recommend_records, compare_records, list_sections, call_indexed_tool. Their descriptions and schemas cost roughly 518 tokens of context every time the server is loaded.

Does the AgentStatus MCP Index server require authentication?

No. We connected to AgentStatus MCP Index without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AgentStatus MCP Index server still maintained?

AgentStatus MCP Index is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.