Cisa Kev logo

Cisa Kev

Query CISA's Known Exploited Vulnerabilities catalog for CVE details, vendors, and recently added entries through MCP.

Install Cisa Kev

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "cisa-kev": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-cisa-kev"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 4 tools correctly (5d ago).

Overview

Cisa Kev exposes CISA's Known Exploited Vulnerabilities catalog through MCP, including actively exploited CVEs and required-action dates. Its tools retrieve the full catalog, look up individual CVEs, list vendors, and filter entries by recency; data comes from CISA's JSON feed and is cached for one hour. Use the hosted Pipeworx endpoint for remote access or run the package locally over stdio without a gateway account.

Use cases

  • Look up a CVE in CISA's KEV catalog
  • Find vulnerabilities added within a chosen number of days
  • List vendors with entries in the KEV catalog
  • Review the complete KEV catalog and its required-action dates

Key features

  • Full CISA KEV catalog retrieval
  • Individual CVE lookup
  • Distinct vendor listing
  • Recent-entry filtering
  • One-hour in-pack data cache
  • Hosted or local stdio operation

Tools4

What Cisa Kev lets your agent do. Expand a tool for its parameters.

Verified live~170 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

11/11 checks healthy over the last 62d

What it can do

From the 4 tools this server returned when we ran it; 4 declare their own safety hints.

Makes network requests · 4Read-only tools · 4
Network at startup4 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age168 days
Maintainers1

Observed 2026-11-03 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · @pipeworx/mcp-cisa-kev (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads435Package downloads in the last 30 days.
Last commit8d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed4Callable tools this server registers over MCP.

How Cisa Kev works

What Cisa Kev does

Cisa Kev makes CISA's Known Exploited Vulnerabilities (KEV) catalog available to MCP clients and HTTP callers. The catalog covers actively exploited CVEs and includes required-action dates alongside other entry metadata. It is intended for agents that need to inspect vulnerability records, identify affected vendors, or find additions made within a recent time window.

The integration is independent and unofficial; it is not affiliated with, endorsed by, or published by CISA.

How it works

The server reads CISA's published JSON feed at https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json. The in-pack data is cached for one hour. No API key is required for the standalone package, and the first calls to the hosted HTTP interface do not require an account.

There are two connection models. The hosted pack endpoint is available at https://gateway.pipeworx.io/cisa-kev/mcp. The same gateway also provides a full endpoint at https://gateway.pipeworx.io/mcp; the pack endpoint lists Cisa Kev's tools directly while both endpoints can reach Pipeworx's broader routing through ask_pipeworx.

The package can instead run as a local stdio MCP process. In that mode, it responds to MCP initialization, tool listing, and tool calls for the Cisa Kev tools only.

Setup and configuration

For a hosted connection, add the pack endpoint to an MCP client:

config.json
{
  "mcpServers": {
    "cisa-kev": {
      "url": "https://gateway.pipeworx.io/cisa-kev/mcp"
    }
  }
}

For local use, configure the package as a command-based server:

config.json
{
  "mcpServers": {
    "cisa-kev": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-cisa-kev"]
    }
  }
}

You can also start it directly with npx -y @pipeworx/mcp-cisa-kev. For HTTP clients, the hosted tools can be called through paths such as POST https://gateway.pipeworx.io/v1/tools/catalog with a JSON request body.

Tools and capabilities

  • catalog() returns the complete catalog with metadata and vulnerability entries.
  • entry(cve_id) retrieves one KEV record by CVE identifier.
  • vendors() returns the distinct vendors represented in the catalog.
  • recent(days) finds entries added during the specified number of preceding days.

The hosted gateway adds shared Pipeworx meta-tools to the pack endpoint's tool list, including ask_pipeworx, discover_tools, search_within, remember, and recall. The local stdio process exposes only the four Cisa Kev tools. With the gateway, ask_pipeworx can route plain-language questions across the wider Pipeworx catalog.

Limitations and notes

The hosted endpoint's tool list is larger than the pack-specific list because of the gateway-wide meta-tools. The exact scope is stated by the MCP initialize response. Local stdio avoids those additional tools but also does not provide the gateway's cross-catalog routing. Because the data is cached for one hour, newly published CISA entries may not appear immediately.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Cisa Kev

Cisa Kev is an MCP server that connects AI agents to CISA's Known Exploited Vulnerabilities catalog. It exposes catalog, entry, vendors, and recent tools for browsing catalog metadata, looking up CVEs, listing vendors, and finding recently added vulnerabilities. It can run through Pipeworx or locally over stdio.

Install it locally by configuring `npx -y @pipeworx/mcp-cisa-kev` as an MCP stdio server. You can also connect to the hosted endpoint at `https://gateway.pipeworx.io/cisa-kev/mcp` without installing the package.

Yes, Cisa Kev works with Cursor through the hosted MCP endpoint. Add `https://gateway.pipeworx.io/cisa-kev/mcp` to Cursor's MCP server configuration, or configure the package locally as a stdio server.

Call the `entry(cve_id)` tool with the CVE identifier. It returns the matching CISA KEV entry; the `catalog()` tool is available when you need the complete catalog instead.

No API key is required for the standalone package, and the first calls to the hosted HTTP interface do not require an account. The package reads CISA's public JSON catalog feed.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewCisa Kev AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/cisa-kev?style=directory)](https://allmcps.com/mcp/cisa-kev)
HTML Embed
<a href="https://allmcps.com/mcp/cisa-kev"><img src="https://allmcps.com/api/badge/cisa-kev?style=directory" alt="Cisa Kev on AllMCPs" /></a>