spot-orbit vs droid.monster — specs
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). droid.monster — specs is an MCP server published by droid.monster. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 |  droid.monster — specs | |
|---|---|---|
| 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.0.0 No figure published 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 | spot-orbit | droid.monster — specs |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (api.droid.monster/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/kwag93/spot-orbit-plugin | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 days ago |
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
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.
droid.monster — specs
Specs of commercially available robots, each figure citing its source document.
How to run each
spot-orbit As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install spot-orbit@claude-communitydroid.monster — specs As a remote MCP server
claude mcp add --transport http specs https://api.droid.monster/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only droid.monster — specs 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
Neither one's marketplaces publish the settings it asks for.
What it can do: spot-orbit · What it can do: droid.monster — specs · 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.