MCP Observatory: one read only walk over every https endpoint in the official registry
io.github.ogasurfproject-jpg/hs-mcp-observatory
Public record of one read only walk over the official MCP registry: who answered, tools, who pays.
This endpoint completed initialize and tools/list. No tool was called.
- Rank
- #2062
- Score
- 82
- Tool tokens
- 461
- Tools
- 6
Tools
Token cost is the o200k count of the tools list JSON, including schemas, before any tool is called.
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
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. r
mcp_observatory_method
How the walk was run, what we got wrong and corrected, and the four rules the report holds itself to.
Nearby in GitHub
Up-to-date code docs for any prompt
MCP server for Financial Modeling Prep API with 250+ financial data tools
Official SerpApi MCP server for Google, Bing, and other search engines.
Comprehensive PostgreSQL documentation and best practices, including ecosystem tools