Rocket Launch Schedule (SpaceX, Falcon, Electron) — buy per-query in-session (launchwatch) vs io.github.christerso/celestial-node
Rocket Launch Schedule (SpaceX, Falcon, Electron) — buy per-query in-session (launchwatch) is an MCP server published by a2awire.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.christerso/celestial-node is an MCP server published by christerso. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.christerso/celestial-node | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 No figure published Not marked · First seen |
Listed Version: 1.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Rocket Launch Schedule (SpaceX, Falcon, Electron) — buy per-query in-session (launchwatch) | io.github.christerso/celestial-node |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (a2awire.com/mcp/data/launchwatch-rocket-launch-schedule-index-b9d878/http) | On your machine (celestialnode-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/ee324/a2awire | github.com/christerso/celestialnode-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 4 days ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Rocket Launch Schedule (SpaceX, Falcon, Electron) — buy per-query in-session (launchwatch)
Rocket launch schedule: SpaceX, Falcon, Electron. $0.01/query, free testnet funds.
io.github.christerso/celestial-node
Real-time space data — ISS tracking, rocket launches, space news, Mars weather, and more
How to run each
Rocket Launch Schedule (SpaceX, Falcon, Electron) — buy per-query in-session (launchwatch) As a remote MCP server
claude mcp add --transport http data-rocket-launch-schedule-spacex https://a2awire.com/mcp/data/launchwatch-rocket-launch-schedule-index-b9d878/httpio.github.christerso/celestial-node As a local MCP server: npm package
claude mcp add --transport stdio celestial-node -- npx -y celestialnode-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Rocket Launch Schedule (SpaceX, Falcon, Electron) — buy per-query in-session (launchwatch) has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Rocket Launch Schedule (SpaceX, Falcon, Electron) — buy per-query in-session (launchwatch) publish no settings it asks for, so we do not compare settings.
What it can do: Rocket Launch Schedule (SpaceX, Falcon, Electron) — buy per-query in-session (launchwatch) · What it can do: io.github.christerso/celestial-node · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.