Ext Ops Panel
Open dashboard
Comparison

Ramparts Security Scanner vs Canli Validation

Ramparts Security Scanner is an MCP server published by highflame-ai. Marketplaces we read that list it: 1 (Docker MCP Catalog). Canli Validation is an MCP server published by arhancanli. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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 ScannerCanli Validation
Docker MCP Catalog Listed
Version: sha256:1ddf4303800e
Forks (GitHub): 20
Pulls (Docker Hub): 35 662
Stars (Docker Hub): 0
Stars (GitHub): 98
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.14.0
Downloads/month (npm): 4 412
Downloads/week (npm): 108
Forks (GitHub): 2
Stars (GitHub): 5
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 Canli Validation
FactRamparts Security ScannerCanli Validation
Marketplaces that list it11
Stars (GitHub) (differs)98 (better)5 (worse)
Pulls (Docker Hub) (differs)35 662No figure on Docker Hub
Forks (GitHub) (differs)20 (better)2 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/ramparts)Remote server (canlicapital.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)2Not published
Environment variables it asks for (differs)1, secrets among them: 03, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/getjavelin/rampartsgithub.com/arhancanli/canlicapital
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 6 h ago

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.

Canli Validation

In its own words, on Official MCP Registry:

Deflated Sharpe and PBO checks. A verdict is not admission to anything and is not a forecast.

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

Canli Validation As a remote MCP server

Claude Code
claude mcp add --transport http canli-validation-mcp https://canlicapital.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: CANLI_KEY (secret), Authorization header

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

Only Canli Validation has a remote endpoint we check. How we check endpoints

Tools each declares

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

Settings each asks for

Only Ramparts Security Scanner asks for

  • RUST_LOG

Only Canli Validation asks for

  • CANLI_API_BASE
  • CANLI_KEY (secret)
  • CANLI_LOCAL

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: Canli Validation · 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