Ext Ops Panel
Open dashboard
Comparison

CVE Exploit Priority (CISA KEV + EPSS) vs io.github.rezearcher/cve-triage

CVE Exploit Priority (CISA KEV + EPSS) is an MCP server published by brunckel. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.rezearcher/cve-triage is an MCP server published by rezearcher. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
MarketplaceCVE Exploit Priority (CISA KEV + EPSS)io.github.rezearcher/cve-triage
Official MCP Registry Listed
Version: 0.1.0
No figure published
Not marked · First seen
Listed
Version: 1.0.0
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

CVE Exploit Priority (CISA KEV + EPSS) vs io.github.rezearcher/cve-triage
FactCVE Exploit Priority (CISA KEV + EPSS)io.github.rezearcher/cve-triage
Marketplaces that list it11
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.apify.com)Remote server (x402-cve-triage.sigrunner.workers.dev/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
RepositoryNot statedNot stated
Changes in the last 7 days00
First seen (differs)2026-10-242026-10-11
Endpoint at the last check (differs)Status out of date: last check 33 h ago returned HTTP 401Status out of date: last check 36 h ago returned HTTP 404

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

CVE Exploit Priority (CISA KEV + EPSS)

In its own words, on Official MCP Registry:

CISA KEV status and EPSS scores for CVE IDs, ranked P1/P2/P3 for patching, via Apify.

io.github.rezearcher/cve-triage

In its own words, on Official MCP Registry:

x402 CVE triage MCP: EPSS + CISA KEV -> exploit priority, $0.01 per query.

How to run each

CVE Exploit Priority (CISA KEV + EPSS)

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

Requires: Authorization header

io.github.rezearcher/cve-triage As a remote MCP server

Claude Code
claude mcp add --transport http cve-triage https://x402-cve-triage.sigrunner.workers.dev/mcp

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

Only the endpoint of CVE Exploit Priority (CISA KEV + EPSS) responded at the last daily check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: CVE Exploit Priority (CISA KEV + EPSS) · What it can do: io.github.rezearcher/cve-triage · Compare two other plugins

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