Remote MCP · Endpoint

Nasa Firms MCP server

No. Nasa Firms answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/nasa-firms
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
89 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
NASA FIRMS MCP — active-fire / thermal-anomaly detections from MODIS and VIIRS.
Listing
From the official MCP registry (active).
Recent checks of Nasa Firms
CheckedResultHandshake
5 hours agoHandshake completed89 ms
9 days agoHandshake completed324 ms
10 days agoHandshake completed1.09 s
11 days agoHandshake completed305 ms
12 days agoHandshake completed177 ms
14 days agoHandshake completed164 ms
14 days agoHandshake completed122 ms
15 days agoHandshake completed1.15 s
17 days agoHandshake completed1.26 s
19 days agoHandshake completed71 ms
22 days agoHandshake completed89 ms
24 days agoHandshake completed1.70 s
26 days agoHandshake completed143 ms
28 days agoHandshake completed1.07 s

The last 14 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.

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