Remote MCP · Endpoint

Star Ninja MCP server

No. Star Ninja answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://stars.2pm.ninja/mcp

The last check completed an MCP handshake.

Registry name
io.github.2pm-ninja/star-ninja
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
414 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Star Ninja reports sky darkness, cloud cover and moonless hours for a night-sky spot you name.
Listing
From the official MCP registry (active).
Recent checks of Star Ninja
CheckedResultHandshake
1 hour agoHandshake completed414 ms
2 days agoHandshake completed433 ms
4 days agoHandshake completed431 ms
6 days agoHandshake completed423 ms
8 days agoHandshake completed432 ms
10 days agoHandshake completed417 ms
12 days agoHandshake completed443 ms
14 days agoHandshake completed443 ms
15 days agoHandshake completed467 ms
16 days agoHandshake completed351 ms
18 days agoHandshake completed430 ms
20 days agoHandshake completed439 ms
22 days agoHandshake completed481 ms
24 days agoHandshake completed429 ms

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

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