
This connects Claude to FIRST.org's Exploit Prediction Scoring System, which estimates the probability that a CVE will be exploited in the wild. It's part of the Pipeworx gateway ecosystem but available as a standalone endpoint. The source doesn't list specific tools, but EPSS typically lets you query probability scores by CVE ID and pull bulk scoring data. Reach for this when you're doing vulnerability prioritization work and want to factor in real world exploit likelihood instead of just CVSS severity. You can call tools directly or use the ask_pipeworx wrapper to query in plain English. Runs over streamable HTTP, so no local setup needed.
FIRST.org EPSS (Exploit Prediction Scoring System) MCP.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
get_epss | EPSS exploit-probability for one or more CVEs. Returns each CVE's EPSS score (0-1 = probability it will be exploited in the wild in the next 30 days) and percentile (how it ranks vs all CVEs). Use to gauge real-world exploit likelihood and prioritize patching — complements CVSS severity (a high-severity CVE with low EPSS may be lower urgency than a moderate-severity one with high EPSS). |
top_exploited | List the CVEs most likely to be exploited, ranked by EPSS score descending. Answers "which vulnerabilities are most likely to be exploited right now" so you can prioritize patching. EPSS is the probability (0-1) a CVE will be exploited in the wild in the next 30 days; this complements CVSS severity rather than replacing it. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"epss": {
"url": "https://gateway.pipeworx.io/epss/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/epss/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Epss data" })
The gateway picks the right tool and fills the arguments automatically.
MIT
curl -X POST https://gateway.pipeworx.io/v1/tools/get_epss \
-H 'Content-Type: application/json' \
-d '{"cve":"CVE-2021-44228"}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/get_epss. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.