Rube vs walkerOS Source Browser
Rube is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). walkerOS Source Browser is an MCP server published by walkeros.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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 |  walkerOS Source Browser | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 4.5.0 Downloads/month (npm): 2 541 Downloads/week (npm): 862 Forks (GitHub): 23 Stars (GitHub): 347 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 | walkerOS Source Browser |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 347 |
| Forks (GitHub) (differs) | No figure on GitHub | 23 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (rube.app/mcp) | On your machine (@walkeros/mcp-source-browser) |
| Transport (differs) | Streamable HTTP | stdio |
| 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/elbwalker/walkeros |
| 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.
walkerOS Source Browser
Generate, parse, and validate walkerOS data-elb HTML tagging attributes
How to run each
Rube As a remote MCP server
claude mcp add --transport http rube https://rube.app/mcpRequires: RUBE_API_KEY (secret)
walkerOS Source Browser As a local MCP server: npm package
claude mcp add --transport stdio source-browser -- npx -y @walkeros/mcp-source-browserCommands 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 walkerOS Source Browser publish no settings it asks for, so we do not compare settings.
What it can do: Rube · What it can do: walkerOS Source Browser · 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.