mcpbeat Sign in

Exploitwatch MCP Server

not responding

Exploitwatch is listed as active in the registry but did not answer our last check. It exposes 1 tools.

Check a dependency list against CISA's live Known Exploited Vulnerabilities catalog.

Uptime history 50 days of history · worst day 0%
50 days agonow
0.0%
Uptime 24h
0 of 91 checks
1
Tools
read from the server
71 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 16 September 2026. No other catalogue keeps this.

18 Sep a tool description was rewritten check_dependencies_against_kev
16 Sep a tool description was rewritten check_dependencies_against_kev

Exploitwatch does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

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 5 min ago.

run in your terminal
claude mcp add exploitwatch --transport http https://www.edgethirteen.com/api/mcp/exploitwatch
Settings → Connectors → Add custom connector, then paste this address
https://www.edgethirteen.com/api/mcp/exploitwatch
~/.codex/config.toml
[mcp_servers.exploitwatch]
url = "https://www.edgethirteen.com/api/mcp/exploitwatch"
.cursor/mcp.json
{
  "mcpServers": {
    "exploitwatch": {
      "url": "https://www.edgethirteen.com/api/mcp/exploitwatch"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "exploitwatch": {
      "type": "http",
      "url": "https://www.edgethirteen.com/api/mcp/exploitwatch"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

dependencies
check_dependencies_against_kev
Check a comma-separated list of software dependency/product names against CISA's live Known Exploited Vulnerabilities (KEV) catalog. Returns any matches with the CVE, vulnerability name, and why it matched. Call this before shipping or during a dependency/security review to catch actively-exploited components, or when working out whether an EU Cyber Resilience Act Article 14 reporting obligation (the 24h early warning / 72h notification / 14-day final report clock) has been triggered. Matching is by name and deliberately errs towards over-matching, so review each hit before acting on it. The free check returns every raw match; the triaged Article 14 exposure report with the notification clock computed and ENISA fields pre-filled is a separate $299 product at https://www.edgethirteen.com/tools/exploit-watch.

Endpoints

URLTransportStateLatencyChecked
https://www.edgethirteen.com/api/mcp/exploitwatch streamable-http answering 71 ms 5 min ago

Alternatives to Exploitwatch

same job, measured the same way
Exploitwatch
by vercel-exploitwatch-kappa

Check dependencies against CISA's real Known Exploited Vulnerabilities feed.

1 tools answering
Cisa Kev MCP
by mrfentmen

Use this MCP server to CISA Known Exploited Vulnerabilities catalog search. Tools include search...

115 installs/wk local only
CISA Known Exploited Vulnerabilities (kevwatch)
by a2awire

CISA KEV catalog: active-exploit alerts, hourly. Register in-session — free testnet funds.

16 tools answering
Dependency Vulnerability Check (OSV)
by brunckel

Known vulnerabilities and fixed versions for npm, PyPI, Go, Maven packages from OSV.dev via Apify.

answering
OSV Dependency Vulnerability Check
by fairquery

Check npm, PyPI, Go and Maven packages or lockfiles against OSV.dev: CVEs, CVSS, fixed versions.

answering
Osv Advisory MCP Server
by cyanheads

Query OSV.dev for package vulnerabilities and batch-audit dependency lists via MCP.

286 installs/wk 5 tools answering
TOPY.AI · AI CSO
by topy

Founders' AI CSO: vulnerabilities, dependencies, secrets, verified-site checks, threat model, fixes.

252 installs/wk answering
Depcheck
by kaneky

Known vulnerabilities for exact package versions from OSV, with fixes. Paid per call, x402.

1 tools answering

Exploitwatch — questions

Answers built from our own checks of this server.

What can Exploitwatch do?
It exposes 1 tools, read directly from the server on our last check. Among them: check_dependencies_against_kev. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Exploitwatch working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 71 ms. The bar chart above shows every period we have measured.
The registry lists Exploitwatch as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Exploitwatch?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Exploitwatch need an API key?
No. Exploitwatch completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.