Rube vs FTX MCP — FactoryTalk Optix MCP Server
Rube is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). FTX MCP — FactoryTalk Optix MCP Server is an MCP server published by asqi-carter. 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 | ||
|---|---|---|
| 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.9 Downloads/month (PyPI): 1 600 Downloads/week (PyPI): 84 Forks (GitHub): 6 Stars (GitHub): 17 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 | FTX MCP — FactoryTalk Optix MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 17 |
| Forks (GitHub) (differs) | No figure on GitHub | 6 |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | Remote server (rube.app/mcp) | On your machine (ftx-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/asqi-carter/ftx-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-14 | 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
Rube
Access to Rube's catalog of remote MCP servers.
FTX MCP — FactoryTalk Optix MCP Server
MCP server for FactoryTalk Optix: author, preview, and verify Studio changes via the emulator.
How to run each
Rube As a remote MCP server
claude mcp add --transport http rube https://rube.app/mcp
Requires: RUBE_API_KEY (secret)
FTX MCP — FactoryTalk Optix MCP Server
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Rube 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 FTX MCP — FactoryTalk Optix MCP Server publish no settings it asks for, so we do not compare settings.
What it can do: Rube · What it can do: FTX MCP — FactoryTalk Optix MCP Server · 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.