Ext Ops Panel
Open dashboard
Comparison

Ramparts Security Scanner vs malchela

Ramparts Security Scanner is an MCP server published by highflame-ai. Marketplaces we read that list it: 1 (Docker MCP Catalog). malchela is a plugin bundle for AI coding tools published by dwmetz. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-20. 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 Scannermalchela
Docker MCP Catalog Listed
Version: sha256:1ddf4303800e
Forks (GitHub): 20
Pulls (Docker Hub): 35 267
Stars (Docker Hub): 0
Stars (GitHub): 98
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 13eabfe
Forks (GitHub): 8
Stars (GitHub): 117
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 malchela
FactRamparts Security Scannermalchela
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)98 (worse)117 (better)
Pulls (Docker Hub) (differs)35 267No figure on Docker Hub
Forks (GitHub) (differs)20 (better)8 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/ramparts)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)2Not published
Environment variables it asks for1, secrets among them: 01, secrets among them: 0
Parts of the bundle (differs)Not a bundle1
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/getjavelin/rampartsgithub.com/dwmetz/malchela
Changes in the last 7 days (differs)02
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.

malchela

In its own words, on Claude Code: claude-plugins-community:

MalChela is a Rust-based malware analysis toolkit for DFIR analysts and malware researchers. It exposes file triage, string extraction with IOC detection and MITRE ATT&CK mapping, YARA rule generation, hash lookup, VirusTotal and MalwareBazaar threat intel queries, and NSRL database checks — all accessible to Claude via MCP server integration.

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

malchela As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install malchela@claude-community

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of malchela publish no list of tools, so we do not compare tools.

Settings each asks for

Only Ramparts Security Scanner asks for

  • RUST_LOG

Only malchela asks for

  • MALCHELA_DIR

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Ramparts Security Scanner · What it can do: malchela · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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