security-audit vs EchelonGraph CVE & Exposure
security-audit is a plugin bundle for AI coding tools published by netresearch. Marketplaces we read that list it: 1 (Community GitHub marketplaces). EchelonGraph CVE & Exposure is an MCP server published by echelongraph.io. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-21. 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
| Marketplace |  security-audit |   EchelonGraph CVE & Exposure |
|---|---|---|
| Community marketplace fabiensalles/claude-marketplace | Listed Version: 2.11.8 Forks (GitHub): 4 Stars (GitHub): 47 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 3.0.2 Downloads/month (npm): 6 379 Downloads/week (npm): 783 Forks (GitHub): 1 Stars (GitHub): 8 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 3.0.2 Downloads/month (npm): 6 379 Downloads/week (npm): 783 Forks (GitHub): 1 Stars (GitHub): 8 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
| Fact | security-audit | EchelonGraph CVE & Exposure |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 47 (better) | 8 (worse) |
| Forks (GitHub) (differs) | 4 (better) | 1 (worse) |
| Last release (differs) | Not published | 2026-10-18 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 0 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | (MIT AND CC-BY-SA-4.0) | MIT |
| Repository (differs) | github.com/netresearch/security-audit-skill | github.com/echelongraph/echelongraph-mcp |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-18 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 days 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
security-audit
Security audit patterns (OWASP, CWE, CVSS) with 80+ checkpoints — by Netresearch
EchelonGraph CVE & Exposure
CVE, KEV, EPSS, SBOM and advisory lookups; per-CVE exposure from Shodan data (© Shodan). Keyless.
How to run each
security-audit As a Claude Code plugin
/plugin marketplace add fabiensalles/claude-marketplace
/plugin install security-audit@fabien-claude-marketplaceEchelonGraph CVE & Exposure As a remote MCP server
claude mcp add --transport http echelongraph-mcp https://mcp.echelongraph.io/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only EchelonGraph CVE & Exposure has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of security-audit nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
The marketplaces of security-audit publish no settings it asks for, so we do not compare settings.
What it can do: security-audit · What it can do: EchelonGraph CVE & Exposure · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.