Ext Ops Panel
Open dashboard
Comparison

spot-orbit vs io.github.christerso/celestial-node

spot-orbit is a plugin bundle for AI coding tools published by kwag93. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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-15. 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

Where each is published
Marketplacespot-orbitio.github.christerso/celestial-node
Claude Code: claude-plugins-community Listed
Version: 7c8f13e
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed 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

spot-orbit vs io.github.christerso/celestial-node
Factspot-orbitio.github.christerso/celestial-node
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (celestialnode-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/kwag93/spot-orbit-plugingithub.com/christerso/celestialnode-mcp
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11

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

spot-orbit

In its own words, on Claude Code: claude-plugins-community:

Boston Dynamics Spot Orbit API explorer, SPX extension builder, and SDK guide. Provides 17 MCP tools for live Orbit API access (robots, runs, anomalies, calendars, webhooks), 5 interactive skills for API exploration, SPX packaging, troubleshooting, and certificate setup, plus 32 reference docs covering Spot hardware, operations, and diagnostics.

io.github.christerso/celestial-node

In its own words, on Official MCP Registry:

Real-time space data — ISS tracking, rocket launches, space news, Mars weather, and more

How to run each

spot-orbit As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install spot-orbit@claude-community

io.github.christerso/celestial-node As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio celestial-node -- npx -y celestialnode-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

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 spot-orbit publish no settings it asks for, so we do not compare settings.

What it can do: spot-orbit · What it can do: io.github.christerso/celestial-node · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built