mcpbeat Sign in

Cve Triage MCP Server

answering

Cve Triage is answering right now. Last checked 6 min ago.

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

Uptime history 47 days of history · worst day 0%
47 days agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
763 ms
Response time
average over 24h
authentication required
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Cve Triage every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add cve-triage --transport http https://x402-cve-triage.sigrunner.workers.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "cve-triage": {
      "url": "https://x402-cve-triage.sigrunner.workers.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.cve-triage]
url = "https://x402-cve-triage.sigrunner.workers.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "cve-triage": {
      "url": "https://x402-cve-triage.sigrunner.workers.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "cve-triage": {
      "url": "https://x402-cve-triage.sigrunner.workers.dev/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://x402-cve-triage.sigrunner.workers.dev/mcp streamable-http needs auth 645 ms 6 min ago

Alternatives to Cve Triage

same job, measured the same way
WalletTriage
by wallettriage

Real-time exploit-exposure risk check for EVM wallets, paid per query via x402 (USDC on Base).

58 installs/wk local only
AIS CVE Priorities — daily exploit-ranked patch list for AI agents
by aislabs

Daily CVE priorities ranked by real exploitation (KEV+EPSS) for AI agents; free teaser, paid full

4 tools answering
Patch Tuesday
by jonnybottles

Query Microsoft Patch Tuesday security updates (MSRC) with EPSS and CISA KEV enrichment

129 installs/wk 1 tools answering
NotCVE — CVE & Vulnerability Intelligence
by notcve

CVE & vulnerability search: 365k+ CVEs/NotCVEs, CVSS, EPSS, CISA KEV, exploits, patches, versions.

answering
Purify Security Feeds
by eason4kim-rocket

Query CISA KEV / EPSS vulnerability feeds with full per-record provenance and auditable versions

local only
Cork MCP
by servosity

Every Cork API operation, plus cross-client risk attribution and exploitability-first vuln triage.

local only
Epss
by pipeworx-io

FIRST.org EPSS (Exploit Prediction Scoring System) MCP.

33 tools answering
Sec Events
by pipeworx-io

SEC 8-K event triage — query our pre-classified mirror of every

35 tools answering

Cve Triage — questions

Answers built from our own checks of this server.

Why is there no tool list for Cve Triage?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Cve Triage working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 763 ms. The bar chart above shows every period we have measured.
How do I connect Cve Triage?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does Cve Triage need an API key?
Yes. Every time we knock, Cve Triage answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Cve Triage?
It answers our handshake in 763 ms on average, which is faster than 15% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.