MCP Observatory: one read only walk over every https endpoint in the official registry
REMOTE · OBSERVATORY.HORIZONSHIELD.DEV
Public record of one read only walk over the official MCP registry: who answered, tools, who pays.
Available components
Last scanned (18 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security54
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 441 tokens (~73/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 4 Oct 26 0
- Stability: 0.97 → pass security
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 4 Sept 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://observatory.horizonshield.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=horizonshield.dev | CN=WE1,O=Google Trust Services,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 9ac22e06bc43af0f13d851565f7c7376 |
| SANs: horizonshield.dev, observatory.horizonshield.dev, *.observatory.horizonshield.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of observatory.horizonshield.dev. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| horizonshield.dev. | present | 2371 | 13 | Verified |
| observatory.horizonshield.dev. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://observatory.horizonshield.dev/mcp | Verified | 200 | |
| http (plaintext) | http://observatory.horizonshield.dev/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
mcp_observatory_disclosure_guide ~48
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mcp_observatory_lookup ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | The full declared endpoint, e.g. https://example.com/mcp |
| host | string | – | A host, e.g. example.com. Returns counts for that host, not a roster. |
No output schema declared.
No examples provided.
mcp_observatory_measure_now ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | https endpoint, e.g. https://example.com/mcp |
No output schema declared.
No examples provided.
mcp_observatory_method ~35
How the walk was run, what we got wrong and corrected, and the four rules the report holds itself to.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mcp_observatory_state ~40
What was measured, when, over what population, and what the measurement cannot tell you. Read this before quoting any number from this server.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mcp_observatory_summary ~41
The counts, as published and as corrected. How many addresses answered, how many tools they exposed, how many stated who compensates their operator.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the MCP Observatory: one read only walk over every https… server?
MCP Observatory: one read only walk over every https… is a hosted endpoint at https://observatory.horizonshield.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · observatory.horizonshield.dev
claude mcp add --transport http ogasurfproject-jpg-hs-mcp-observatory 'https://observatory.horizonshield.dev/mcp'
What is the MCP Observatory: one read only walk over every https… server?
MCP Observatory: one read only walk over every https… is listed in the public MCP registry as 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 page covers its hosted endpoint (https://observatory.horizonshield.dev/mcp).
Is the MCP Observatory: one read only walk over every https… server safe to use?
MCP Observatory: one read only walk over every https… scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MCP Observatory: one read only walk over every https… server expose?
MCP Observatory: one read only walk over every https… exposes 6 tools: mcp_observatory_state, mcp_observatory_summary, mcp_observatory_lookup, mcp_observatory_disclosure_guide, mcp_observatory_measure_now, mcp_observatory_method. Their descriptions and schemas cost roughly 379 tokens of context every time the server is loaded.
Does the MCP Observatory: one read only walk over every https… server require authentication?
No. We connected to MCP Observatory: one read only walk over every https… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MCP Observatory: one read only walk over every https… server still maintained?
MCP Observatory: one read only walk over every https… is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.