Ext Ops Panel
Open dashboard
Comparison

dependabot-triage vs EchelonGraph CVE & Exposure

dependabot-triage is a plugin bundle for AI coding tools published by aaronpowell. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). 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-26. 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
Marketplacedependabot-triageEchelonGraph CVE & Exposure
Copilot CLI: github/awesome-copilot Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.1.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.1.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

dependabot-triage vs EchelonGraph CVE & Exposure
Factdependabot-triageEchelonGraph CVE & Exposure
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)8 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last release (differs)Not published2026-10-25
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
LicenceMITMIT
Repository (differs)github.com/aaronpowell/github-copilot-dependabot-canvasgithub.com/echelongraph/echelongraph-mcp
Changes in the last 7 days (differs)05
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 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

dependabot-triage

In its own words, on Copilot CLI: github/awesome-copilot:

Triage Dependabot alerts and recommend safe, evidence-based dependency updates.

EchelonGraph CVE & Exposure

In its own words, on Official MCP Registry:

CVE, KEV, EPSS, SBOM and advisory lookups; per-CVE exposure from Shodan data (© Shodan). Keyless.

How to run each

dependabot-triage

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

EchelonGraph CVE & Exposure As a remote MCP server

Claude Code
claude mcp add --transport http echelongraph-mcp https://mcp.echelongraph.io/mcp

Commands 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 dependabot-triage nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

The marketplaces of dependabot-triage publish no settings it asks for, so we do not compare settings.

What it can do: dependabot-triage · What it can do: EchelonGraph CVE & Exposure · Compare two other plugins

Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built