mcpbeat Sign in

Cisa Cybersecurity MCP Server

answering

Cisa Cybersecurity MCP Server is answering right now. Last checked 9 min ago. 351 installs a week from npm. It exposes 7 tools. Last commit 1 Nov 2026.

CISA KEV with BOD 26-04 deadlines, SSVC prioritization, and the ICS advisory corpus (CSAF). Keyless.

Installs per day peak 234 · avg 30 · +85% w/w
a month agotoday
Uptime history 49 days of history · worst day 92%
49 days agonow
100.0%
Uptime 24h
91 of 91 checks
7
Tools
read from the server
507 ms
Response time
average over 24h
351
Installs / week
npm and PyPI

What changed 32

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

1 Nov 6 tools changed the parameters they ask for cisa_check_cve_status, cisa_get_advisory, cisa_get_alerts and 3 more
1 Nov 2 tool descriptions were rewritten cisa_get_advisory, cisa_get_alerts
1 Nov a tool changed version
14 Oct 4 tools changed the parameters they ask for cisa_get_advisory, cisa_get_alerts, cisa_search_ics_advisories and 1 more
14 Oct a tool changed version
14 Oct a tool description was rewritten cisa_get_advisory
9 Oct a tool changed version
25 Sep 4 tools changed the parameters they ask for6 times that day cisa_check_cve_status, cisa_get_advisory, cisa_search_ics_advisories and 1 more
25 Sep 2 tool descriptions were rewritten cisa_check_cve_status, cisa_search_ics_advisories
25 Sep a tool changed version2 times that day
and 9 more, back to 22 September 2026

Nothing serious here today

Today is the operative word: we check Cisa Cybersecurity MCP Server every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

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

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

Available tools 7

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

cisa
cisa_check_cve_status
Check CVE IDs against the CISA Known Exploited Vulnerabilities catalog — up to 200 per call, served from a cached catalog snapshot at no upstream cost. Returns, per CVE, whether it is in KEV and if so the date added, the federal remediation due date, days remaining or days overdue, which binding operational directive the entry cites, the required action text, whether it is linked to ransomware campaigns, whether it falls in the three-day forensic-triage tier, CISA's own vendor and product labels, associated CWEs, and the reference URLs parsed from the entry's notes. A CVE that is not in KEV is a normal result, not an error. For a large batch, detail "summary" keeps only the triage fields — the deadline and overdue status, directive, ransomware and forensic-triage flags, and vendor and product labels — and drops the descriptive text, CWEs, and references, so a full batch stays compact. The CWE IDs returned chain directly into the cwe filter of cisa_search_kev and cisa_search_ics_advisories, and the parsed NVD reference gives the canonical record for scoring detail. For the reverse direction — which ICS advisories cover a CVE — pass it as cve to cisa_search_ics_advisories, or set inKev there to list the advisories covering any KEV CVE.
cisa_get_advisory
Read one CISA industrial control system advisory: product definitions and relationship component references; per-CVE CVSS score, vector, and CWE; vendor remediations, flags, and threats; sectors; and revision history. Large advisories return a section outline with byte sizes and vulnerability CVE IDs. Re-call with sections, cves for named vulnerabilities, or productIds for exact product definitions referenced by vulnerability status, scores, remediations, flags, or threats. Product IDs are case-sensitive; relationship selection does not expand components. Every response carries source URLs and attribution. Find advisory IDs with cisa_search_ics_advisories.
cisa_get_alerts
List what CISA has published recently — its combined advisory feed, its alerts feed, or its ICS advisory feed. Cursors continue within the current 30-item rolling window; upstream provides no pagination, history, or date-range query. The window's coverage varies from about a week to about two months depending on the feed. For ICS advisory history beyond the window, use cisa_search_ics_advisories, which covers the full corpus back to 2010.
cisa_get_ssvc
Fetch the SSVC decision points CISA publishes per CVE as a CVE Authorized Data Publisher — Exploitation, Automatable, and Technical Impact — along with the CVSS score and CWE CISA contributes where present, and compute the BOD 26-04 remediation timeline those values imply for the asset exposure you supply. The computed timeline applies CISA's published decision table to CISA's published decision points and your stated exposure; it is not a compliance determination and it is not CISA's own due-date assignment, which is reported separately when the CVE is in KEV and can differ. Not every CVE is enriched — a miss returns found false with guidance rather than an error. Call cisa_list_reference with topic ssvc_values for the decision-point vocabulary.
cisa_list_reference
Decode the vocabulary the other CISA tools take as input. Topics cover the BOD 26-04 remediation timeline table and what each tier means, the KEV record fields and their value domains, the SSVC decision points CISA publishes, the critical-infrastructure sector names as the advisory corpus spells them, advisory ID formats, CVSS severity bands, and the freshness of the data this server currently holds. Call this before constructing filters for cisa_search_kev or cisa_search_ics_advisories, and whenever another tool's recovery hint points here.
cisa_search_ics_advisories
Search the CISA industrial control system advisory corpus — every CSAF 2.0 advisory covering PLC, HMI, SCADA, building-automation, and medical-device products from 2010 onward. Filter by vendor, product, CVE, CWE, CVSS range, severity band, critical-infrastructure sector, advisory series, publication date, revision date, or whether an advisory covers a CVE in the CISA Known Exploited Vulnerabilities catalog, and run full-text search over advisory titles and product names. Sector filtering reaches only advisories that carry a sector note, which begins in 2017; the response reports how many documents a sector filter can never match. Returns advisory IDs for cisa_get_advisory, the CVEs each advisory covers and which of them are in KEV, and the source URL and attribution every advisory response carries.
cisa_search_kev
Search the CISA Known Exploited Vulnerabilities catalog across every entry in the cached snapshot. Filter by vendor or product using CISA's own labels, by name substring, by CWE, by the date an entry was added, by due date, by overdue status, by ransomware linkage, by the three-day forensic-triage tier, or by which binding operational directive the entry cites. Results are paged and sortable by due date or date added. Vendor and product values are CISA's free-text labels, not CPE names — call cisa_list_reference for the field vocabulary before guessing one. The catalog records additions but carries no per-record modified timestamp, so dateAddedFrom answers "what is new since D" while a revised due date on an existing entry is not detectable from the feed.

Endpoints

URLTransportStateLatencyChecked
https://cisa-cybersecurity.caseyjhand.com/mcp streamable-http answering 607 ms 9 min ago

Alternatives to Cisa Cybersecurity MCP Server

same job, measured the same way
Normaradar – Spain Business Compliance
by fergonsan

Legal obligations of Spanish companies by profile, with deadlines and official sources.

answering
WCAG 2.2 Compliance
by veduis

WCAG 2.2 audits with corrected markup, verified fix examples, and U.S. ADA deadlines.

local only
Feedmyagent
by makash

Agent-readable feed: AI/agent tech news, security advisories, compliance deadlines, and live events.

84 installs/wk 7 tools answering
CISA Cybersecurity & ICS Advisories — buy per-query in-session (cisaalerts)
by a2awire

CISA advisories & ICS alerts: new CVEs, remediation. Register in-session — free testnet funds.

17 tools answering
Company Gibraltar
by company-gibraltar

Gibraltar company tools: corporate tax, compliance deadlines, and PDF form generation.

54 installs/wk local only
Company Gi
by company-gibraltar

Gibraltar company tools: corporate tax, compliance deadlines, and PDF form generation.

52 installs/wk local only
Openapi Security Contract Lint
by jmshinhwa

Finds the lines in an OpenAPI file that publish an endpoint with no authentication, an API key in th

112 installs/wk local only
Regulatory Radar
by jdhart81

California, US, and global climate compliance scans with source-linked deadlines.

5 tools answering

Cisa Cybersecurity MCP Server — questions

Answers built from our own checks of this server.

What can Cisa Cybersecurity MCP Server do?
It exposes 7 tools, read directly from the server on our last check. Among them: cisa_check_cve_status, cisa_get_advisory, cisa_get_alerts, cisa_get_ssvc, cisa_list_reference, cisa_search_ics_advisories and 1 more. 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 Cisa Cybersecurity MCP Server working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 507 ms. The bar chart above shows every period we have measured.
How do I connect Cisa Cybersecurity MCP Server?
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 Cisa Cybersecurity MCP Server need an API key?
No. Cisa Cybersecurity MCP Server completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Cisa Cybersecurity MCP Server?
It answers our handshake in 507 ms on average, which is faster than 23% 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.
How many people use Cisa Cybersecurity MCP Server?
The npm package @cyanheads/cisa-cybersecurity-mcp-server was installed 351 times in the last week. Week over week that is +85%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Cisa Cybersecurity MCP Server open source?
The code is open source: it is published under the Apache-2.0 licence, written in TypeScript, 1 stars on GitHub and 5 open issues. The licence covers the code in the repository, not the hosted service at cisa-cybersecurity.caseyjhand.com, which runs on its operator's own terms.