All servers · Other

MCP Observatory: one read only walk over every https endpoint in the official registry

io.github.ogasurfproject-jpg/hs-mcp-observatory · v0.1.1

Measured by MCP Station

Description written by the publisher, not verified

Public record of one read only walk over the official MCP registry: who answered, tools, who pays.

Connect

claude mcp add --transport http hs-mcp-observatory https://observatory.horizonshield.dev/mcp

{
  "mcpServers": {
    "hs-mcp-observatory": {
      "url": "https://observatory.horizonshield.dev/mcp"
    }
  }
}

Tools as reported by the server

• 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
• mcp_observatory_method
  How the walk was run, what we got wrong and corrected, and the four rules the report holds itself to.

Repository · Website · JSON · Text for agents · Registry updated 2026-09-04