gap — graph as policy vs RoboSelect360 - Independent Humanoid Robot Intelligence
gap — graph as policy is a plugin bundle for AI coding tools published by graph-as-policy authors. Marketplaces we read that list it: 1 (Community GitHub marketplaces). RoboSelect360 - Independent Humanoid Robot Intelligence is an MCP server published by roboselect360.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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 |  RoboSelect360 - Independent Humanoid Robot Intelligence | |
|---|---|---|
| Community marketplace graph-robots/graph-as-policy | Listed Version: not stated Forks (GitHub): 17 Stars (GitHub): 168 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.3 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 | gap — graph as policy | RoboSelect360 - Independent Humanoid Robot Intelligence |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 168 | No figure on GitHub |
| Forks (GitHub) (differs) | 17 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.roboselect360.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/graph-robots/graph-as-policy | Not stated |
| Changes in the last 7 days (differs) | 2 | 4 |
| First seen (differs) | 2026-10-20 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 30 h 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
gap — graph as policy
Operate the gap robot-graph engine: search robot skill registries (open-robot-skills and your own), check tool/model/skill capabilities (gap check), run graphs in LIBERO sim, generate graphs from language, author skill bundles and registries with scaffolded unit tests, debug traces, and execute safety-gated real-robot tasks.
RoboSelect360 - Independent Humanoid Robot Intelligence
Independent humanoid robot intelligence: capabilities, real cost, supply chain. Free and paid tiers.
How to run each
gap — graph as policy As a Claude Code plugin
/plugin marketplace add graph-robots/graph-as-policy
/plugin install gap@gapRoboSelect360 - Independent Humanoid Robot Intelligence As a remote MCP server
claude mcp add --transport http humanoid-robots https://mcp.roboselect360.com/mcp --header "X-API-Key: <YOUR_X_API_KEY>"Requires: X-API-Key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only RoboSelect360 - Independent Humanoid Robot Intelligence 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: gap — graph as policy · What it can do: RoboSelect360 - Independent Humanoid Robot Intelligence · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.