Remote MCP · Endpoint

Nasa Ads MCP server

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

UpLast checked 5 hours ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/nasa-ads
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
77 ms
Tools exposed
47 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
NASA ADS — the Astrophysics Data System, api.adsabs.harvard.edu.
Listing
From the official MCP registry (active).
Recent checks of Nasa Ads
CheckedResultHandshake
5 hours agoHandshake completed77 ms
9 days agoHandshake completed151 ms
10 days agoHandshake completed95 ms
11 days agoHandshake completed147 ms
12 days agoHandshake completed201 ms
14 days agoHandshake completed86 ms
15 days agoHandshake completed124 ms
15 days agoHandshake completed513 ms
17 days agoHandshake completed222 ms
19 days agoHandshake completed917 ms
22 days agoHandshake completed1.36 s
24 days agoHandshake completed3.32 s
26 days agoHandshake completed1.25 s
28 days agoFailed - the request timed out—

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 28 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 Ads and makes no claim about it beyond what these checks measured.