Remote MCP · Endpoint

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

No. MCP Observatory: one read only walk over every https endpoint in the official registry answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://observatory.horizonshield.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.ogasurfproject-jpg/hs-mcp-observatory
Transport
Streamable HTTP
Protocol negotiated
2025-11-25
Handshake latency
143 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Public record of one read only walk over the official MCP registry: who answered, tools, who pays.
Website
https://shield.the-horizons-innovation.com/verify-directory/survey/1/
Repository
https://github.com/ogasurfproject-jpg/horizon-shield
Listing
From the official MCP registry (active).
Recent checks of MCP Observatory: one read only walk over every https endpoint in the official registry
CheckedResultHandshake
1 hour agoHandshake completed143 ms
1 day agoHandshake completed206 ms
2 days agoHandshake completed161 ms
3 days agoHandshake completed187 ms
4 days agoHandshake completed126 ms
5 days agoHandshake completed161 ms
6 days agoHandshake completed155 ms
9 days agoHandshake completed101 ms
11 days agoHandshake completed244 ms
14 days agoHandshake completed110 ms
16 days agoHandshake completed204 ms
18 days agoHandshake completed133 ms
20 days agoHandshake completed189 ms
22 days agoHandshake completed189 ms
24 days agoHandshake completed153 ms
26 days agoHandshake completed115 ms
28 days agoHandshake completed317 ms
29 days agoHandshake completed336 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with MCP Observatory: one read only walk over every https endpoint in the official registry and makes no claim about it beyond what these checks measured.