Developer · Remote MCP server
Exploitwatch
Check dependencies against CISA's real Known Exploited Vulnerabilities feed.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
app.vercel.exploitwatch-kappa/exploitwatch- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-13
- Updated
- 2026-09-13
- Publisher
- app.vercel.exploitwatch-kappa
- Namespace
- Namespace verified by the MCP Registry via the domain exploitwatch-kappa.vercel.app or a parent domain of it · how
- Website
- exploitwatch-kappa.vercel.app
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://exploitwatch-kappa.vercel.app/api/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- exploitwatch 1.0.0 · protocol 2025-03-26
- Tools discovered
- 1:
check_kev - Checked on
- 2026-10-05
How to connect Exploitwatch
Exploitwatch is a remote MCP server: there is nothing to install. Its endpoint is https://exploitwatch-kappa.vercel.app/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| ExerciseapiGive your AI coding agent direct access to 2,198+ exercises via exerciseapi.dev. | Local · stdio |
| Exit1 Uptime MonitoringSet up uptime monitoring from your editor: create checks, configure alerts, query uptime history. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Exploit Intelligence Platform - CVE, Vulnerability and Exploit DatabaseReal-time CVE, exploit, and vulnerability intelligence for AI assistants (350K+ CVEs, 115K+ PoCs) | Remote & Local · HTTP, stdioLive check: ✗ no handshake |
| Exploit-DB New Exploits & Proof-of-Concepts - buy per-query in-session (exploitdb)Exploit-DB: new public exploits & PoCs, daily. Register in-session - free testnet funds. | Remote · HTTPLive check: ✓ handshake |
| ExploitwatchCheck a dependency list against CISA's live Known Exploited Vulnerabilities catalog. | Remote · HTTPLive check: ✗ no handshake |
| ExpoYour Expo and EAS project in natural language: up to date SDK docs, cloud builds (status, logs, trig. | Remote · HTTPLive check: ✓ handshake |
| ExposureGuardDomain security scanning for AI agents. A-F grades, 8 checks, fix snippets. | Local · stdio |
| extensiondev MCPBuild, run, inspect, and publish browser extensions from any MCP client. 31 tools, 11 browsers. | Local · stdio |