Rube vs Invokary Platform Requirements
Rube is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Invokary Platform Requirements is an MCP server published by invokary.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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 |   Invokary Platform Requirements | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.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 | Rube | Invokary Platform Requirements |
|---|---|---|
| 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 (rube.app/mcp) | Remote server (mcp.invokary.com/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/invokary/platform-requirements-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-14 | Responded 44 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
Rube
Access to Rube's catalog of remote MCP servers.
Invokary Platform Requirements
What Claude, ChatGPT, Cursor and the MCP Registry require to list an MCP connector or plugin.
How to run each
Rube As a remote MCP server
claude mcp add --transport http rube https://rube.app/mcpRequires: RUBE_API_KEY (secret)
Invokary Platform Requirements As a remote MCP server
claude mcp add --transport http platform-requirements https://mcp.invokary.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of Invokary Platform Requirements responded at the last daily 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 Invokary Platform Requirements publish no settings it asks for, so we do not compare settings.
What it can do: Rube · What it can do: Invokary Platform Requirements · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.