Ext Ops Panel
Open dashboard
Comparison

Ramparts Security Scanner vs pyobfus-mcp

Ramparts Security Scanner is an MCP server published by highflame-ai. 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-09. 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
MarketplaceRamparts Security Scannerpyobfus-mcp
Docker MCP Catalog Listed
Version: sha256:1ddf4303800e
Forks (GitHub): 20
Pulls (Docker Hub): 36 055
Stars (Docker Hub): 0
Stars (GitHub): 99
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

Ramparts Security Scanner vs pyobfus-mcp
FactRamparts Security Scannerpyobfus-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)99 (better)11 (worse)
Pulls (Docker Hub) (differs)36 055No figure on Docker Hub
Forks (GitHub) (differs)20 (better)4 (worse)
Last release (differs)Not published2026-10-30
Where it runs (differs)On your machine (mcp/ramparts)On your machine (pyobfus-mcp)
Transportstdiostdio
Tools it declares (differs)2Not published
Environment variables it asks for (differs)1, secrets among them: 0Not published
LicenceApache-2.0Apache-2.0
Repository (differs)github.com/getjavelin/rampartsgithub.com/zhurong2020/pyobfus
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11

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

Ramparts Security Scanner

In its own words, on Docker MCP Catalog:

A comprehensive security scanner for MCP servers with YARA rules and static analysis capabilities.

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

Ramparts Security Scanner As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio ramparts -- docker run -i --rm mcp/ramparts

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.

Tools each declares

The marketplaces of pyobfus-mcp publish no list of tools, so we do not compare tools.

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: Ramparts Security Scanner · 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