Remote MCP · Endpoint

Tanod Sky MCP server

No. Tanod Sky answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://tanod.dev/mcp/sky

The last check completed an MCP handshake.

Registry name
dev.tanod/sky
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
313 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Aviation and space data: METAR/TAF, airports, space weather, aurora, asteroids, satellite passes.
Website
https://tanod.dev/
Listing
From the official MCP registry (active).
Recent checks of Tanod Sky
CheckedResultHandshake
1 hour agoHandshake completed313 ms
6 hours agoHandshake completed832 ms
2 days agoHandshake completed356 ms
4 days agoHandshake completed304 ms
7 days agoHandshake completed295 ms
9 days agoHandshake completed311 ms
11 days agoHandshake completed326 ms
13 days agoHandshake completed281 ms
15 days agoHandshake completed1.88 s
18 days agoHandshake completed257 ms
20 days agoHandshake completed258 ms
21 days agoHandshake completed774 ms
23 days agoHandshake completed288 ms

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

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 Tanod Sky and makes no claim about it beyond what these checks measured.