Remote MCP · Endpoint

Rocket Launch Schedule (SpaceX, Falcon, Electron) — buy per-query in-session (launchwatch) MCP server

No. Rocket Launch Schedule (SpaceX, Falcon, Electron) — buy per-query in-session (launchwatch) answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://a2awire.com/mcp/data/launchwatch-rocket-launch-schedule-index-b9d878/http

The last check completed an MCP handshake.

Registry name
com.a2awire/data-rocket-launch-schedule-spacex
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
50 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Rocket launch schedule: SpaceX, Falcon, Electron. $0.01/query, free testnet funds.
Website
https://a2awire.com/data/launchwatch-rocket-launch-schedule-index-b9d878
Repository
https://github.com/ee324/a2awire
Listing
From the official MCP registry (active).
Recent checks of Rocket Launch Schedule (SpaceX, Falcon, Electron) — buy per-query in-session (launchwatch)
CheckedResultHandshake
2 hours agoHandshake completed50 ms
2 days agoHandshake completed178 ms
4 days agoHandshake completed136 ms
6 days agoHandshake completed97 ms
7 days agoHandshake completed49 ms
8 days agoHandshake completed45 ms
9 days agoHandshake completed622 ms
12 days agoHandshake completed436 ms
14 days agoHandshake completed385 ms
15 days agoHandshake completed210 ms
17 days agoHandshake completed456 ms
18 days agoHandshake completed153 ms
19 days agoHandshake completed125 ms
20 days agoHandshake completed402 ms
20 days agoHandshake completed393 ms
22 days agoHandshake completed370 ms
23 days agoHandshake completed266 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.

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 Rocket Launch Schedule (SpaceX, Falcon, Electron) — buy per-query in-session (launchwatch) and makes no claim about it beyond what these checks measured.