# io.github.cyanheads/cisa-cybersecurity-mcp-server (remote · cisa-cybersecurity.caseyjhand.com)

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

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `cisa-cybersecurity.caseyjhand.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/cyanheads-cisa-cybersecurity-mcp-server/cisa-cybersecurity.md), [page](https://verifymcp.io/servers/cyanheads-cisa-cybersecurity-mcp-server/cisa-cybersecurity)
- npm · `@cyanheads/cisa-cybersecurity-mcp-server`: 43/100, [markdown](https://verifymcp.io/servers/cyanheads-cisa-cybersecurity-mcp-server/cyanheads-cisa-cybersecurity-mcp-server.md), [page](https://verifymcp.io/servers/cyanheads-cisa-cybersecurity-mcp-server/cyanheads-cisa-cybersecurity-mcp-server)

## Channel facts

- Endpoint: `https://cisa-cybersecurity.caseyjhand.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 8210 tokens (~122/item across 67 items; 7 tools + 60 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the io.github.cyanheads/cisa-cybersecurity-mcp-server server?

io.github.cyanheads/cisa-cybersecurity-mcp-server is a hosted endpoint at https://cisa-cybersecurity.caseyjhand.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http cyanheads-cisa-cybersecurity-mcp-server 'https://cisa-cybersecurity.caseyjhand.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "cyanheads-cisa-cybersecurity-mcp-server": {
      "url": "https://cisa-cybersecurity.caseyjhand.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cyanheads-cisa-cybersecurity-mcp-server": {
      "type": "http",
      "url": "https://cisa-cybersecurity.caseyjhand.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.cyanheads-cisa-cybersecurity-mcp-server]
url = "https://cisa-cybersecurity.caseyjhand.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyanheads-cisa-cybersecurity-mcp-server": {
      "type": "remote",
      "url": "https://cisa-cybersecurity.caseyjhand.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cyanheads-cisa-cybersecurity-mcp-server --url 'https://cisa-cybersecurity.caseyjhand.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cyanheads-cisa-cybersecurity-mcp-server:
    url: "https://cisa-cybersecurity.caseyjhand.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "cyanheads-cisa-cybersecurity-mcp-server": {
      "Transport": "http",
      "Url": "https://cisa-cybersecurity.caseyjhand.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cyanheads-cisa-cybersecurity-mcp-server -t streamable-http -u 'https://cisa-cybersecurity.caseyjhand.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "cyanheads-cisa-cybersecurity-mcp-server": {
      "type": "http",
      "url": "https://cisa-cybersecurity.caseyjhand.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 70)

First indexed and scored.

## MCP tools (7)

### `cisa_list_reference` (~176 tokens)

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.

Input parameters:

- `topic` (string, required): Which reference block to return: directives (BOD 26-04 Table 1 and its definitions), kev_fields, ssvc_values, sectors, advisory_id_formats, severity_bands, or sources (what this server currently hold…

Output parameters:

- `definitions` (array): Topic directives only — supporting definitions from the directive text.
- `entries` (array): The decoded terms for this topic.
- `error` (object): Present when the call failed. Absent on success.
- `sources` (object): Topic sources only — what this server currently holds, read from in-process state.
- `summary` (string): What this topic covers and when to reach for it.
- `supersedes` (array): Topic directives only — the directives BOD 26-04 supersedes and revokes.
- `timelineTable` (array): Topic directives only — all sixteen rows of BOD 26-04 Appendix A, Table 1.
- `title` (string): Human-readable title for the topic.
- `topic` (string): The topic that was decoded.

### `cisa_check_cve_status` (~230 tokens)

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. The CWE IDs returned chain directly into cisa_search_kev's CWE filter, and the parsed NVD reference gives the canonical record for scoring detail.

Input parameters:

- `cveIds` (array, required): CVE identifiers to check, up to 200 per call. The whole batch costs zero upstream requests, so a full CVE alias list from a dependency audit can be checked in one call.

Output parameters:

- `asOf` (string): The UTC date daysUntilDue and overdue were computed against, YYYY-MM-DD.
- `catalog` (object): Which catalog snapshot answered this call.
- `error` (object): Present when the call failed. Absent on success.
- `foundCount` (integer): How many of the requested CVEs are in the catalog.
- `notFoundCount` (integer): How many of the requested CVEs are not in the catalog.
- `notice` (string): Guidance when none of the supplied CVE IDs are in the catalog.
- `results` (array): One result per requested CVE, in the order supplied.

### `cisa_search_kev` (~521 tokens)

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.

Input parameters:

- `cursor` (string): Opaque pagination cursor from a previous call. Omit for the first page.
- `cveIdPrefix` (string): Year scope for the CVE ID, e.g. CVE-2026.
- `cwe` (string): Exact CWE identifier, e.g. CWE-362. Excludes the 175 entries with no CWEs.
- `dateAddedFrom` (string): Earliest date added, inclusive, YYYY-MM-DD.
- `dateAddedTo` (string): Latest date added, inclusive, YYYY-MM-DD.
- `directive` (string): Which directive the entry cites. "none" selects the 1,277 entries citing neither.
- `dueAfter` (string): Earliest due date, inclusive, YYYY-MM-DD.
- `dueBefore` (string): Latest due date, inclusive, YYYY-MM-DD.
- `forensicTriage` (boolean): True selects the BOD 26-04 three-day forensic-triage tier (58 entries).
- `limit` (integer): Maximum entries per page.
- `nameContains` (string): Strict token match over the vulnerability name and short description: every token must appear. No fuzzy fallback.
- `order` (string): Sort direction.
- `overdue` (boolean): True selects entries whose due date is strictly before the echoed asOf date.
- `product` (string): Case-insensitive substring of CISA's own product label. 694 distinct values.
- `ransomware` (boolean): True selects entries CISA has linked to ransomware campaigns (360 entries).
- `sortBy` (string): Field to sort by.
- `vendorProject` (string): Case-insensitive substring of CISA's own vendor label. 283 distinct values.

Output parameters:

- `appliedFilters` (object): The filters the server actually applied, as it parsed them.
- `asOf` (string): The UTC date overdue and daysUntilDue were computed against, YYYY-MM-DD.
- `cap` (integer): The page limit that was applied.
- `catalog` (object): Which catalog snapshot answered this call.
- `cursor` (string): Opaque cursor for the next page. Absent when this is the last page.
- `error` (object): Present when the call failed. Absent on success.
- `hasMore` (boolean): Whether more matches exist beyond this page.
- `notice` (string): Guidance when nothing matched.
- `results` (array): Matching KEV entries for this page.
- `shown` (integer): Entries returned on this page.
- `snapshotCaveat` (string): Disclosure that additions are queryable but revisions are not detectable.
- `totalCount` (integer): Total matches before paging.
- `truncated` (boolean): True when the page limit capped this result.

### `cisa_get_ssvc` (~275 tokens)

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.

Input parameters:

- `assetExposure` (string): Whether the affected asset is reachable by unauthenticated or untrusted entities over public networks. The one BOD 26-04 decision point CISA cannot publish. "unknown" returns both arms so the spread…
- `cveIds` (array, required): CVE identifiers to look up, up to 50 per call — lower than cisa_check_cve_status's 200-CVE cap because each CVE needs its own live enrichment lookup rather than a cached batch check.

Output parameters:

- `echo` (object): The request as the server parsed it.
- `error` (object): Present when the call failed. Absent on success.
- `foundCount` (integer): How many CVEs carry published SSVC decision points.
- `notFoundCount` (integer): How many CVEs do not.
- `notice` (string): Guidance when nothing was enriched, or when a decision timestamp predates KEV.
- `results` (array): One result per requested CVE, in the order supplied.

### `cisa_search_ics_advisories` (~578 tokens)

Search the CISA industrial control system advisory corpus — 3,926 CSAF 2.0 documents covering PLC, HMI, SCADA, building-automation, and medical-device products from 2010 onward. Filter by vendor, product, CVE, CVSS range, severity band, critical-infrastructure sector, advisory series, publication date, or revision date, 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 the source URL and attribution every advisory response carries.

Input parameters:

- `cursor` (string): Opaque pagination cursor from a previous call. Omit for the first page.
- `cve` (string): Exact CVE membership. The corpus covers 12,321 distinct CVEs.
- `cvssMax` (number): Maximum value of the advisory's maximum CVSS base score, inclusive.
- `cvssMin` (number): Minimum value of the advisory's maximum CVSS base score, inclusive.
- `limit` (integer): Maximum advisories per page.
- `order` (string): Sort direction. Under relevance, desc means most relevant first.
- `product` (string): Case-insensitive substring of a product name.
- `publishedFrom` (string): Earliest initial release date, inclusive, YYYY-MM-DD.
- `publishedTo` (string): Latest initial release date, inclusive, YYYY-MM-DD.
- `publisher` (string): coordinator selects CISA-authored advisories (2,863); other selects republished vendor advisories (1,063).
- `q` (string): Full-text search over advisory titles, vendor names, and product names. Tokens are AND-combined; FTS5 operators in the input are neutralized rather than honored.
- `revisedFrom` (string): Earliest current release date, inclusive, YYYY-MM-DD.
- `revisedTo` (string): Latest current release date, inclusive, YYYY-MM-DD.
- `sector` (string): Critical-infrastructure sector, matched against the normalized sector set. Multiple is the sentinel the corpus uses for an advisory affecting many sectors.
- `series` (string): Advisory series: ICSA (3,738 documents) or ICSMA medical devices (188).
- `severity` (string): Severity band of the advisory's maximum CVSS score.
- `sortBy` (string): Field to sort by. relevance requires q and ranks by FTS5 bm25.
- `vendor` (string): Case-insensitive substring of a vendor label. Vendor names are unnormalized upstream — the same company appears under several spellings — so this is substring, not exact.

Output parameters:

- `appliedFilters` (object): The filters the server actually applied.
- `cap` (integer): The page limit that was applied.
- `cursor` (string): Opaque cursor for the next page. Absent when this is the last page.
- `cvssCoverage` (string): Disclosure of derived-band and no-score coverage under a score filter.
- `error` (object): Present when the call failed. Absent on success.
- `hasMore` (boolean): Whether more matches exist beyond this page.
- `mirror` (object): Which index state answered this call.
- `notice` (string): Guidance when nothing matched.
- `results` (array): Matching advisories for this page.
- `sectorCoverage` (string): Disclosure of how many advisories a sector filter can never match.
- `shown` (integer): Advisories returned on this page.
- `totalCount` (integer): Total matches before paging.
- `truncated` (boolean): True when the page limit capped this result.

### `cisa_get_advisory` (~216 tokens)

Read one CISA industrial control system advisory in full: affected products flattened from the CSAF product tree into vendor, product, and version ranges; per-CVE CVSS score, vector, and CWE; remediations with their category and vendor instructions; critical-infrastructure sectors; and the revision history. Large advisories return a section outline instead of the whole document — re-call with the sections you need. Republished vendor advisories carry the originating vendor's text; every response reports the source URL and attribution. Find advisory IDs with cisa_search_ics_advisories.

Input parameters:

- `advisoryId` (string, required): Advisory identifier, e.g. ICSA-26-260-07 or ICSMA-26-253-02. Case-insensitive; an optional revision suffix is a single letter a-f or a numeric -N. A trailing .json is stripped.
- `sections` (array): Sections to return. Omit for the whole document, or for its outline when the document overflows the inline budget.

Output parameters:

- `acknowledgments` (array): Acknowledgment entries.
- `advisory` (object): Advisory identity, dates, and attribution. Always kept, including on a section selection.
- `error` (object): Present when the call failed. Absent on success.
- `found` (boolean): Whether an advisory with that ID is in the index.
- `guidance` (string): What to do instead, present when found is false.
- `kind` (string): full when the document is returned; outline when only the section listing is.
- `outlineNotice` (string): Outline arm — how to call cisa_get_advisory for specific sections.
- `products` (object): Affected products and version ranges.
- `references` (array): Document-level references.
- `revisionHistory` (array): Revision history, oldest first as published.
- `sections` (array): Outline arm — the sections available, largest first, with their byte sizes.
- `summary` (object): Narrative notes and sector classification.
- `vulnerabilities` (array): Vulnerabilities the advisory covers, with scores, remediations, and product status.

### `cisa_get_alerts` (~212 tokens)

List what CISA has published recently — its combined advisory feed, its alerts feed, or its ICS advisory feed. Each feed is a rolling window of exactly 30 items with no history, no pagination, and no date-range query, so 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.

Input parameters:

- `feed` (string): Which feed to read: advisories (all.xml, ~8 days of coverage), alerts (alerts.xml, ~8 weeks), or ics (ics-advisories.xml, ~2.5 weeks).
- `limit` (integer): Maximum items to return. The 30 ceiling is the upstream window, not a server choice.
- `since` (string): Keep only items published on or after this date, YYYY-MM-DD. Filters within the fetched window; it cannot reach back beyond it.

Output parameters:

- `cap` (integer): The limit that was applied.
- `effectiveQuery` (string): The since filter as applied, and how many window items it excluded.
- `error` (object): Present when the call failed. Absent on success.
- `feed` (string): The feed that was read.
- `feedTitle` (string): The channel title the feed declares.
- `feedUrl` (string): The absolute feed URL this window came from.
- `items` (array): Items from the current window, newest first as published.
- `notice` (string): Guidance when the since filter excluded every item.
- `shown` (integer): Items returned.
- `truncated` (boolean): True when the limit capped the returned items.
- `window` (object): What the fetched window covers.
- `windowCaveat` (string): That the feed has no history, no pagination, and no date query.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cyanheads-cisa-cybersecurity-mcp-server/cisa-cybersecurity#diagnostics

## Score history

- 2026-09-20: 70

## Common questions

### What is the io.github.cyanheads/cisa-cybersecurity-mcp-server server?

io.github.cyanheads/cisa-cybersecurity-mcp-server is listed in the public MCP registry as io.github.cyanheads/cisa-cybersecurity-mcp-server. CISA KEV with BOD 26-04 deadlines, SSVC prioritization, and the ICS advisory corpus (CSAF). Keyless. This page covers its hosted endpoint (https://cisa-cybersecurity.caseyjhand.com/mcp).

### Is the io.github.cyanheads/cisa-cybersecurity-mcp-server server safe to use?

io.github.cyanheads/cisa-cybersecurity-mcp-server scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.cyanheads/cisa-cybersecurity-mcp-server server expose?

io.github.cyanheads/cisa-cybersecurity-mcp-server exposes 7 tools: cisa_list_reference, cisa_check_cve_status, cisa_search_kev, cisa_get_ssvc, cisa_search_ics_advisories, and 2 more. Their descriptions and schemas cost roughly 2,208 tokens of context every time the server is loaded.

### Does the io.github.cyanheads/cisa-cybersecurity-mcp-server server require authentication?

No. We connected to io.github.cyanheads/cisa-cybersecurity-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.cyanheads/cisa-cybersecurity-mcp-server server still maintained?

io.github.cyanheads/cisa-cybersecurity-mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://cisa-cybersecurity.caseyjhand.com/mcp
- Repository: https://github.com/cyanheads/cisa-cybersecurity-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/cyanheads-cisa-cybersecurity-mcp-server/cisa-cybersecurity.xml
- Changelog JSON feed: https://verifymcp.io/servers/cyanheads-cisa-cybersecurity-mcp-server/cisa-cybersecurity.json
- HTML version of this page: https://verifymcp.io/servers/cyanheads-cisa-cybersecurity-mcp-server/cisa-cybersecurity