cisa-cybersecurity-mcp-serverBLOCK
CISA Known Exploited Vulnerabilities with BOD 26-04 deadlines, SSVC prioritization, and the full ICS advisory corpus (CSAF) via MCP. Keyless. STDIO or Streamable HTTP.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
@cyanheads/cisa-cybersecurity-mcp-server CISA Known Exploited Vulnerabilities with BOD 26-04 deadlines, SSVC prioritization, and the full ICS advisory corpus (CSAF) via MCP. Keyless. STDIO or Streamable HTTP. 7 Tools • 2 Resources
[](./CHANGELOG.md) [](./LICENSE) [](https://github.com/users/cyanheads/packages/container/package/cisa-cybersecurity-mcp-server) [](https://modelcontextprotocol.io/) [](https://www.npmjs.com/package/@cyanheads/cisa-cybersecurity-mcp-server) [](https://www.typescriptlang.org/) [](https://bun.sh/)
[](https://github.com/cyanheads/cisa-cybersecurity-mcp-server/releases/latest/download/cisa-cybersecurity-mcp-server.mcpb) [](https://cursor.com/en/install-mcp?name=cisa-cybersecurity-mcp-server&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIkBjeWFuaGVhZHMvY2lzYS1jeWJlcnNlY3VyaXR5LW1jcC1zZXJ2ZXIiXX0=) [](https://vscode.dev/redirect?url=vsco
5056b2583c36OBSERVED · 2026-10-12Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add cisa-cybersecurity-mcp-server -- npx -y @cyanheads/[email protected]
claude mcp add cisa-cybersecurity-mcp-server -- npx -y @cyanheads/[email protected]
Trust audit
BLOCKgrade F · trust 43/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | FAIL |
| L2 | Instruction surface (what it tells the agent) | FAIL |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (2 observation(s))
- Network
- declared (2 observation(s))
- Shell
- declared (8 observation(s))
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (22)
**Seed orientation context when the next moves are predictable.** Piggybacking a compact snapshot alongside the primary result — recent activity, tracked state, a few reference items — does two things
- **Mirror a bulk upstream instead of paginating it live.** When the server wraps a large or slow API whose corpus is queried far more than it changes, sync it once into a persistent local index and q
const tsc = await exec([join(ROOT_DIR, 'node_modules', '.bin', 'tsc'), '-p', project], 'tsc');
const alias = await exec(
exec(cmd: string[], options: { cwd: string }): Promise<ShellResult> {':(glob)**/.netrc',
| **Server credential** | The server's own upstream key is missing, or the upstream rejects it (401/403) | `ConfigurationError` — translated in the service, since the automatic status mapping yields `
Prereq: a GitHub PAT with `read:org` + `read:user` scopes stored in Keychain under the service name `mcp-publisher-github-pat`:
2. **No `git stash`, no `git reset --hard`, no `git restore .`, no `git clean -f`, no `git checkout -- .`.** These bypass safety and risk silent data loss. Read-only git (`status`, `diff`, `log`, `sho
.mcpbignore
} from '../../../fixtures/csaf-documents.js';
import { buildTarGzResponse } from '../../../fixtures/tar.js';import { buildKevFeedBody } from '../../../fixtures/kev-feed.js';import { FULL_ADVISORY, SPARSE_ADVISORY } from '../../fixtures/csaf-documents.js';import { DRIFTING_CATALOG_COUNT } from '../../helpers/catalog-counts.js';`
${canonical}`,const whitespace = fc.constantFrom(' ', '\t', '\n', '\r', '\v', '\f', ' ', '
', ' ', '');@cyanheads/mcp-ts-core, better-sqlite3, fast-xml-parser, node-cron, pino-pretty, zod, @socketsecurity/bun-security-scanner, depcheck
- [ ] `.codex-plugin/mcp.json` updated — server name key is the unscoped repo name; every user-supplied variable (API key, contact email, instance URL) is listed in `env_vars` so Codex forwards it fro
- [ ] `.codex-plugin/mcp.json` updated — server name key is the unscoped repo name; every user-supplied variable (API key, contact email, instance URL) is listed in `env_vars` so Codex forwards it fro
On every transport, the server refreshes the index once at startup and then on `CISA_CSAF_REFRESH_CRON`, and polls KEV on `CISA_KEV_REFRESH_CRON`. Server processes that share one index — every stdio s
Gates applied: critical_finding, instruction_override, no_behavioural_pass, undeclared_transfer.
5056b2583c36full audit observations/trust-audit/mcp-server/cyanheads__cisa-cybersecurity-mcp-server.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-12 | 5056b2583c36 | BLOCK | F | 43 | first audit |
Questions
What is the cisa-cybersecurity-mcp-server MCP server?
CISA Known Exploited Vulnerabilities with BOD 26-04 deadlines, SSVC prioritization, and the full ICS advisory corpus (CSAF) via MCP. Keyless. STDIO or Streamable HTTP.
Is cisa-cybersecurity-mcp-server safe to connect to an agent?
No — not without reading the findings first. The audit graded it F (43/100) and found 9 critical or high issues in the source. Each one is listed on this page with the file and line it is on.
What credentials does cisa-cybersecurity-mcp-server need?
No credential environment variables were found in its source, so it appears to need none.
How does cisa-cybersecurity-mcp-server run?
It speaks stdio and streamable-http, so it runs as a local process your client starts. It is published on npm as @cyanheads/cisa-cybersecurity-mcp-server at 0.3.1.
How current is this page?
The grade is for one exact copy of the source (5056b2583c36), read on 2026-10-12. The repository is watched and re-audited when it changes.