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

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

使うべきか

品質と安全性

B
説明の品質
93%
スキーマの完全性
52%
命名の品質
77%
ポイズニングのリスク
100%
権限の一致
100%
プロトコルへの準拠
100%

検出事項(1)

  • LOWTool 'mcp_observatory_disclosure_guide' name length outside 3-30 rangemcp_observatory_disclosure_guide 内

ツール定義とプロトコルへの準拠に関する自動分析に基づいています。

コンテキストコスト

~487トークン数(ツール定義)
~260 B一般的なレスポンスサイズ
注意への影響は最小限(128k コンテキストの 0.38%)

これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。

インストール

ワンクリックインストール

これを `claude_desktop_config.json` ファイルに追加してください:

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

リモートエンドポイント

https://observatory.horizonshield.dev/mcpstreamable-http

できること

ツール一覧

ツール(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.

入力スキーマ

{
  "type": "object",
  "properties": {}
}
⚪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.

入力スキーマ

{
  "type": "object",
  "properties": {}
}
⚪mcp_observatory_lookup(address, host)

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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "address": {
      "type": "string",
      "description": "The full declared endpoint, e.g. https://example.com/mcp"
    },
    "host": {
      "type": "string",
      "description": "A host, e.g. example.com. Returns counts for that host, not a roster."
    }
  }
}
⚪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.

入力スキーマ

{
  "type": "object",
  "properties": {}
}
🟡mcp_observatory_measure_now(address)

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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "address": {
      "type": "string",
      "description": "https endpoint, e.g. https://example.com/mcp"
    }
  },
  "required": [
    "address"
  ]
}
⚪mcp_observatory_method

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

入力スキーマ

{
  "type": "object",
  "properties": {}
}

コミュニティ

このサーバーを評価する

エビデンス

最近の観測

検証済みバージョンは記録されていませんツール 6 件
検証済みバージョンは記録されていませんツール 6 件
検証済みバージョンは記録されていませんツール 6 件