io.github.cyanheads/cisa-cybersecurity-mcp-server
v0.3.2CISA KEV with BOD 26-04 deadlines, SSVC prioritization, and the ICS advisory corpus (CSAF). Keyless.
Endpoint health
online- Last checked
- 11/20/2026, 9:18:09 AM
- Latency
- 248 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:io.github.cyanheads%2Fcisa-cybersecurity-mcp-server
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"io.github.cyanheads/cisa-cybersecurity-mcp-server": {
"url": "https://cisa-cybersecurity.caseyjhand.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
7 shown · authentication unknown
cisa_check_cve_status
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.
Schema valid · SHA-256 d2d05c486267…
View input schema
{ "type": "object", "properties": { "cveIds": { "minItems": 1, "maxItems": 1000, "type": "array", "items": { "type": "string", "pattern": "^CVE-[0-9]{4}-[0-9]{4,19}$", "description": "One CVE identifier, e.g. CVE-2025-39964. Case and surrounding whitespace are normalized." }, "description": "CVE identifiers to check, up to 1,000 accepted and 200 processed per call. Oversized batches return normalized unprocessedIds for a follow-up call unless normalization is disabled. The whole batch costs zero upstream requests — pair a large batch with detail \"summary\"." }, "detail": { "default": "full", "description": "full returns every field of each in-KEV entry. summary returns only cveId, inKev, dateAdded, dueDate, daysUntilDue, overdue, directive, vendorProject, product, knownRansomwareCampaignUse, and forensicTriage — the triage view for a large batch. Not-in-KEV results are the same under both.", "type": "string", "enum": [ "full", "summary" ] } }, "required": [ "cveIds" ], "$schema": "https://json-schema.org/draft/2020-12/schema", "additionalProperties": false }
Connections
streamable-http
https://cisa-cybersecurity.caseyjhand.com/mcp