Ext Ops Panel
Open dashboard
Comparison

Rube vs pyobfus-mcp

Rube is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). pyobfus-mcp is an MCP server published by zhurong2020. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-08. 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

Where each is published
MarketplaceRubepyobfus-mcp
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.17
Downloads/month (PyPI): 502
Downloads/week (PyPI): 124
Forks (GitHub): 4
Stars (GitHub): 11
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 0.3.17
Downloads/month (PyPI): 502
Downloads/week (PyPI): 124
Forks (GitHub): 4
Stars (GitHub): 11
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

Rube vs pyobfus-mcp
FactRubepyobfus-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub11
Forks (GitHub) (differs)No figure on GitHub4
Last release (differs)Not published2026-10-30
Where it runs (differs)Remote server (rube.app/mcp)On your machine (pyobfus-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
LicenceApache-2.0Apache-2.0
Repository (differs)Not statedgithub.com/zhurong2020/pyobfus
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Status out of date: no HTTP response at the last check 45 h agono 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

In its own words, on Docker MCP Catalog:

Access to Rube's catalog of remote MCP servers.

pyobfus-mcp

In its own words, on Official MCP Registry:

9 local Python protection tools, delivery checks and traceback reverse mapping. No telemetry.

How to run each

Rube As a remote MCP server

Claude Code
claude mcp add --transport http rube https://rube.app/mcp

Requires: RUBE_API_KEY (secret)

pyobfus-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio pyobfus-mcp -- uvx pyobfus-mcp

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 pyobfus-mcp publish no settings it asks for, so we do not compare settings.

What it can do: Rube · What it can do: pyobfus-mcp · 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. Package data comes from the Python Package Index (pypi.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built