Remote MCP · Endpoint

Nasa Power MCP server

No. Nasa Power answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/nasa-power/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/nasa-power
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
106 ms
Tools exposed
39 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
NASA POWER MCP — Prediction of Worldwide Energy Resources
Listing
From the official MCP registry (active).
Recent checks of Nasa Power
CheckedResultHandshake
1 hour agoHandshake completed106 ms
2 days agoHandshake completed65 ms
4 days agoHandshake completed53 ms
5 days agoHandshake completed64 ms
7 days agoHandshake completed66 ms
8 days agoHandshake completed107 ms
9 days agoHandshake completed52 ms
12 days agoHandshake completed44 ms
13 days agoHandshake completed93 ms
15 days agoHandshake completed140 ms
17 days agoHandshake completed46 ms
18 days agoHandshake completed45 ms
19 days agoHandshake completed36 ms
20 days agoHandshake completed104 ms
21 days agoHandshake completed45 ms
21 days agoHandshake completed37 ms
23 days agoHandshake completed44 ms

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

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