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

io.github.ogasurfproject-jpgPublished by GitHub account ogasurfproject-jpgv0.1.1Updated Oct 27, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingSecurity & Monitoring

Overview

AI-generated overview

Read-only public record of one survey walk over the official MCP registry: counts, per-address lookup, disclosure field guide, and a live single-address probe.

What you can do
  • Read the survey's scope, population, date and stated limits before quoting numbers
  • Get aggregate counts as published and as corrected, including how many addresses answered and how many stated who compensates their operator
  • Look up one address or host you already hold, with the record hash and recompute procedure
  • See how servers that disclosed a payer did it, with observed field names and counts
  • Probe one https address now for MCP support and an agent card, read only and rate limited
  • Read the method so the walk can be redone
When to use it
Useful when you need to check or cite what the MCP registry endpoints looked like on the survey date, or to quickly test whether a specific MCP address speaks MCP and carries an agent card. It is not a directory, so it only helps for addresses you already have.
Requirements
Remote streamable-http endpoint, stateless, no authentication and no environment variables or headers declared. Network access to the endpoint is needed; the live probe is rate limited.
Before you install
The record is one walk on one day; a refusal can be correct behaviour, and a missing payer field is not a finding about the operator. The live probe contacts an address you supply, so only point it at hosts you are entitled to test. It does not change the published record.

Installation

In SourceWeft

  1. Open MCP Observatory: one read only walk over every https endpoint in the official registry in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.ogasurfproject-jpg%2Fhs-mcp-observatory/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "observatory-one-read-only-walk-over-ever": {
      "type": "http",
      "url": "https://observatory.horizonshield.dev/mcp"
    }
  }
}

README

hs-mcp-observatory

A public record of what answered when every https endpoint declared in the official MCP registry was contacted once, read only, on 2026-08-23. It is not a directory and it does not list addresses: you look up an address you already hold, or ask for the aggregate.

Endpoint: https://observatory.horizonshield.dev/mcp (streamable-http, stateless, no auth). Health: /health. One address without MCP: /lookup?address=https://example.com/mcp.

Tools

  • mcp_observatory_state: what was measured, when, over what population, and what the measurement cannot tell you. Read this before quoting any number.
  • mcp_observatory_summary: the counts as published and as corrected.
  • mcp_observatory_lookup: what happened when one address was contacted, or an aggregate for one host, with the record hash and the procedure to recompute it.
  • mcp_observatory_disclosure_guide: how the servers that stated who compensates their operator actually did it, as observed, with counts.
  • mcp_observatory_measure_now: contact one https address now, read only, and report whether it speaks MCP, carries an agent card, and whether that card names who compensates the operator. Rate limited.
  • mcp_observatory_method: the procedure, so anyone can redo it.

Limits, stated in the server itself: the published record is one walk on one day. A refusal can be correct behaviour. Absence of a payer field in an agent card on that day is all the record says; it is not a finding about the operator.

Report: https://shield.the-horizons-innovation.com/verify-directory/survey/1/ Raw walk: https://shield.the-horizons-innovation.com/verify-directory/survey/data/survey1_walk_2026-08-23_run2.jsonl Recompute: https://shield.the-horizons-innovation.com/verify-directory/recompute/

Registry: io.github.ogasurfproject-jpg/hs-mcp-observatory, published from this directory with the MCP registry publish workflow (server_dir = workers/hs-mcp-observatory).

Source: workers/hs-mcp-observatory/README.md at commit 21012e4

Tools

6

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.

Takes no parameters.

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.

Takes no parameters.

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.

Parametershostaddress

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.

Takes no parameters.

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.

Parametersaddressrequired

mcp_observatory_method

How the walk was run, what we got wrong and corrected, and the four rules the report holds itself to.

Takes no parameters.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts