Exploitwatch MCP Server

by edgethirteen-www Your server? Claim it

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 4 days of history · worst day 36%

4 days agonow

34.8%

Uptime 24h

32 of 92 checks

Tools

read from the server

742 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 77.6% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add exploitwatch --transport http https://www.edgethirteen.com/api/mcp/exploitwatch

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "exploitwatch": {
      "url": "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

{
  "mcpServers": {
    "exploitwatch": {
      "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

URL	Transport	State	Latency	Checked
https://www.edgethirteen.com/api/mcp/exploitwatch	streamable-http	answering	30 ms	7 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

by pipeworx-io

CISA Known Exploited Vulnerabilities catalog

35 tools answering

CISA Known Exploited Vulnerabilities (kevwatch)

by a2awire

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

16 tools answering

Cisa Kev MCP

by csoai-org

CISA Known Exploited Vulnerabilities feed + remediation deadlines for US federal + critical infr...

138 installs/wk local only

Osv Advisory MCP Server

by cyanheads

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

101 installs/wk 4 tools answering

AgentGuard — security checks for AI agents

by shuaicongxiaomai

Secret, CVE and dependency-vulnerability scanning for AI agents (free, OSV.dev).

local only

NotCVE — CVE & Vulnerability Intelligence

by notcve

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

answering

VulnFeed

by novadyne-hq

Dependency vulnerability scanner with EPSS scoring. 9 MCP tools. Free tier + x402.

110 installs/wk local only

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 32 of 92 checks got a reply (34.8%), average response time 742 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 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.

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.

How fast is Exploitwatch?

It answers our handshake in 742 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.