MCP Observatory: one read only walk over every https endpoint in the official registry
Public record of one read only walk over the official MCP registry: who answered, tools, who pays.
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeRead-only
What it can do
What data it sees
Do you need an account
No: the server works without sign-in
Public record of one read only walk over the official MCP registry: who answered, tools, who pays.
Server tool list (6)
Raw names from tools/list. Only developers need these.
| mcp_observatory_state | What was measured, when, over what population, and what the measurement cannot tell you. Read this before quoting any number from this server. |
| mcp_observatory_summary | The counts, as published and as corrected. How many addresses answered, how many tools they exposed, how many stated who compensates their operator. |
| mcp_observatory_lookup | What happened when we contacted one address, or an aggregate for one host. Returns the record hash and the procedure to recompute it. There is no tool here that lists addresses; you must already hold the one you are asking about. |
| mcp_observatory_disclosure_guide | How the 152 servers that stated who compensates their operator actually did it - the field names observed in the wild, with counts. Not a specification we invented. |
| mcp_observatory_measure_now | Contact one https address now and report what we see: whether it speaks MCP, whether it carries an agent card, and whether that card names who compensates the operator. Read only; no tool is called. robots.txt is read first and honoured. This does NOT change the published record - the next full walk does that. Rate limited, because it contacts somebody else's server on your behalf. |
| mcp_observatory_method | How the walk was run, what we got wrong and corrected, and the four rules the report holds itself to. |