MCP Observatory: one read only walk over every https endpoint in the official registry
io.github.ogasurfproject-jpg/hs-mcp-observatoryPublic record of one read only walk over the official MCP registry: who answered, tools, who pays.
Score: 100/100
Handshake verified by our own probe.
Tools · 6
What was measured, when, over what population, and what the measurement cannot tell you. Read this before quoting any number from this server.
The counts, as published and as corrected. How many addresses answered, how many tools they exposed, how many stated who compensates their operator.
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 …
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.
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. r…
How the walk was run, what we got wrong and corrected, and the four rules the report holds itself to.
How to use
Claude Desktop or claude.ai: add a custom connector (Customize → Connectors; on Team and Enterprise plans an owner adds it under Organization settings → Connectors) with this server URL: https://observatory.horizonshield.dev/mcp
Cursor or Cline: add to your MCP config:
{
"mcpServers": {
"mcp_observatory:_one_read_only_walk_over_every_https_endpoint_in_the_official_registry": {
"url": "https://observatory.horizonshield.dev/mcp",
"transport": "streamable-http"
}
}
}