Back to MCP servers

Agent Commons

https://mcp.agent-commons.org/mcp
● healthy

Verified playbooks for websites: check before your agent browses, report how it went after.

Transport
streamable-http
Auth
—
Cost
—
Protocol revision
2025-11-25
negotiated, not declared

MCP readiness

B · 88/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B+, 92.9/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 10/10 initialize and tools/list both answered.
Live MCP endpoint 25/25 Endpoint answers the MCP initialize handshake (251 ms).
Protocol revision 8/10 Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 15/15 4/4 probes succeeded; final after 5 probes in 30 days.
Tool declaration 10/10 Lists 4 tool(s) with descriptions.
Verified identity 7/10 Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Freshness + modern flags 4/5 seen in a source within 7 days.
Auth declaration 0/5 How to authenticate is not stated.
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Responsive (251 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness
Higher than 95% of peers
This listing 88 · peer median 81
Latency
Faster than 79% of peers
This listing 159 ms · peer median 326 ms

Where it loses the most points, and how to win them back

  • Auth declaration −5 — State how to authenticate (an auth scheme, or that none is needed).
    Now: How to authenticate is not stated.
  • Verified identity −3 — Claim the listing and prove control of its domain.
    Now: Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
  • Protocol revision −2 — Support the current protocol revision.
    Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

mcp-registry since 2026-11-09

How to connect

MCP endpoint (streamable-http)
https://mcp.agent-commons.org/mcp
JSON-RPC initialize probe
curl -X POST https://mcp.agent-commons.org/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://agent-commons.org/install