Ext Ops Panel
Open dashboard
Comparison

Ramparts Security Scanner vs Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory

Ramparts Security Scanner is an MCP server published by highflame-ai. Marketplaces we read that list it: 1 (Docker MCP Catalog). Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory is an MCP server published by agentdiet.dev. Marketplaces we read that list it: 1 (Official MCP Registry). 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 ScannerAssay A2A, MCP & x402 Pre-Flight Verifier & Observatory
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
Official MCP Registry Not listed Listed
Version: 0.7.32
No figure published
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 Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory
FactRamparts Security ScannerAssay A2A, MCP & x402 Pre-Flight Verifier & Observatory
Marketplaces that list it11
Stars (GitHub) (differs)98No figure on GitHub
Pulls (Docker Hub) (differs)35 267No figure on Docker Hub
Forks (GitHub) (differs)20No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/ramparts)Remote server (assay.agentdiet.dev/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)2Not published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/getjavelin/rampartsNot stated
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-19
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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.

Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory

In its own words, on Official MCP Registry:

Live behavioral security verifier, schema auditor, and trust oracle for A2A, MCP & x402 agents.

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

Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory As a remote MCP server

Claude Code
claude mcp add --transport http assay https://assay.agentdiet.dev/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 Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory publish no settings it asks for, so we do not compare settings.

What it can do: Ramparts Security Scanner · What it can do: Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory · 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.

Where the data comes from: how the catalog is built