Rube vs Wafeq
Rube is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Wafeq is an MCP server published by ohneben. 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 |  Rube |  Wafeq |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.1.0 Forks (GitHub): 0 Stars (GitHub): 1 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 | Wafeq |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 1 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (rube.app/mcp) | On your machine (ghcr.io/ohneben/wafeq-mcp:2.1.0) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 6, secrets among them: 3 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/ohneben/wafeq-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 | 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.
Wafeq
Wafeq accounting API: all 251 endpoints as safety-categorized MCP tools, over stdio or HTTP.
How to run each
Rube As a remote MCP server
claude mcp add --transport http rube https://rube.app/mcpRequires: RUBE_API_KEY (secret)
Wafeq As a local MCP server: Docker image
claude mcp add --env "MCP_AUTH_TOKEN=<YOUR_MCP_AUTH_TOKEN>" --env "MCP_TRANSPORT=<YOUR_MCP_TRANSPORT>" --env "WAFEQ_ACCESS_TOKEN=<YOUR_WAFEQ_ACCESS_TOKEN>" --env "WAFEQ_API_KEY=<YOUR_WAFEQ_API_KEY>" --transport stdio wafeq-mcp -- docker run -i --rm -e MCP_AUTH_TOKEN -e MCP_TRANSPORT -e WAFEQ_ACCESS_TOKEN -e WAFEQ_API_KEY ghcr.io/ohneben/wafeq-mcp:2.1.0Requires: MCP_AUTH_TOKEN (secret), MCP_TRANSPORT, WAFEQ_ACCESS_TOKEN (secret), WAFEQ_API_KEY (secret)
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
Only Rube asks for
RUBE_API_KEY (secret)
Only Wafeq asks for
MCP_AUTH_TOKEN (secret)MCP_TRANSPORTWAFEQ_ACCESS_TOKEN (secret)WAFEQ_API_BASE_URLWAFEQ_API_KEY (secret)WAFEQ_TOOL_GROUPS
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Rube · What it can do: Wafeq · 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.