Skip to content

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

io.github.ogasurfproject-jpg/hs-mcp-observatoryogasurfproject-jpgstreamable-httpv0.1.1Scanned

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

6 tools: 4 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 4 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the MCP Observatory: one read only walk over every https endpoint in the official re… can do

The MCP Observatory: one read only walk over every https endpoint in the official re… is published by the GitHub account ogasurfproject-jpg. It has 6 tools. It can create or change data (4 tools: mcp_observatory_state, mcp_observatory_disclosure_guide, mcp_observatory_measure_now and mcp_observatory_method), but cannot delete data. 2 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 0.1.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 4Claude Code: ask
  • mcp_observatory_disclosure_guideHow the 152 servers that stated who compensates their operator actually did it - the field names observed in the wild, with counts.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_nowContact 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • mcp_observatory_methodHow the walk was run, what we got wrong and corrected, and the four rules the report holds itself to.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    How the walk was run, what we got wrong and corrected, and the four rules the report holds itself to.
  • mcp_observatory_stateWhat was measured, when, over what population, and what the measurement cannot tell you.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    What was measured, when, over what population, and what the measurement cannot tell you. Read this before quoting any number from this server.
Only reads 2Show 2 read-only tools
  • mcp_observatory_lookupWhat happened when we contacted one address, or an aggregate for one host.No findings

    Why it is in this group

    • The name "mcp_observatory_lookup" says "lookup": a word for reading.
    Description, as the server wrote it
    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_summaryThe counts, as published and as corrected.No findings

    Why it is in this group

    • The description's first verb is "count": a word for reading.
    Description, as the server wrote it
    The counts, as published and as corrected. How many addresses answered, how many tools they exposed, how many stated who compensates their operator.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:24 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-11-25
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://observatory.horizonshield.dev/mcp: tools/list returned 6 tools to an anonymous client, including mcp_observatory_state (write), mcp_observatory_disclosure_guide (write), mcp_observatory_measure_now (write), mcp_observatory_method (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__hs-observatory__mcp_observatory_summary",
      "mcp__hs-observatory__mcp_observatory_lookup"
    ],
    "ask": [
      "mcp__hs-observatory__mcp_observatory_state",
      "mcp__hs-observatory__mcp_observatory_disclosure_guide",
      "mcp__hs-observatory__mcp_observatory_measure_now",
      "mcp__hs-observatory__mcp_observatory_method"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as hs-observatory. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.ogasurfproject-jpg/hs-mcp-observatory/verify?hash=e66172ae3dc686cf579ef76cf9b5595a26a3c6642d3d58e7579ed142d194d3d3" | jq -e '.changed == false'

Pinned hash e66172ae3dc6, from Nov 21, 2026, 10:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.ogasurfproject-jpg/hs-mcp-observatory/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.ogasurfproject-jpg/hs-mcp-observatory
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.ogasurfproject-jpg/hs-mcp-observatory.svg)](https://radar.anlyon.com/servers/io.github.ogasurfproject-jpg/hs-mcp-observatory)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:42 UTC.

MCP Observatory: one read only walk over every https endpoint in the official re…: questions and answers

Answered from the scan above, not from the publisher's description.

Is the MCP Observatory: one read only walk over every https endpoint in the official re… safe?

No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the MCP Observatory: one read only walk over every https endpoint in the official re… delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the MCP Observatory: one read only walk over every https endpoint in the official re… do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the MCP Observatory: one read only walk over every https endpoint in the official re… have?

6 tools: 4 write, 2 read. mcp_observatory_state, mcp_observatory_disclosure_guide, mcp_observatory_measure_now, mcp_observatory_method, mcp_observatory_summary and mcp_observatory_lookup.

Does the MCP Observatory: one read only walk over every https endpoint in the official re… need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the MCP Observatory: one read only walk over every https endpoint in the official re… send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the MCP Observatory: one read only walk over every https endpoint in the official re… changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.