Remote MCP · Endpoint

The Observatory MCP server

No. The Observatory answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://observatory.mgorsky.net/mcp

The last check completed an MCP handshake.

Registry name
net.mgorsky/observatory
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
442 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
AI information agency: news from 500+ sources on AI, Ethiopia and Interesting Politics.
Listing
From the official MCP registry (active).
Recent checks of The Observatory
CheckedResultHandshake
8 hours agoHandshake completed442 ms
10 days agoHandshake completed240 ms
11 days agoHandshake completed194 ms
11 days agoHandshake completed188 ms
13 days agoHandshake completed175 ms
15 days agoHandshake completed201 ms
15 days agoHandshake completed178 ms
16 days agoHandshake completed250 ms
17 days agoHandshake completed297 ms
19 days agoHandshake completed404 ms
22 days agoHandshake completed588 ms
24 days agoHandshake completed204 ms
26 days agoHandshake completed571 ms
29 days agoHandshake completed1.37 s

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

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.

Listing data comes from the official MCP registry. Glide is not affiliated with The Observatory and makes no claim about it beyond what these checks measured.