# io.github.cyanheads/nist-nvd-mcp-server (remote · nist-nvd.caseyjhand.com)

Search and audit NIST NVD CVEs by keyword, severity, CWE, CISA KEV status, and CPE.

- Trust score: 88/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `nist-nvd.caseyjhand.com`: 88/100 (this document), [markdown](https://verifymcp.io/servers/cyanheads-nist-nvd-mcp-server/nist-nvd.md), [page](https://verifymcp.io/servers/cyanheads-nist-nvd-mcp-server/nist-nvd)
- npm · `@cyanheads/nist-nvd-mcp-server`: 39/100, [markdown](https://verifymcp.io/servers/cyanheads-nist-nvd-mcp-server/cyanheads-nist-nvd-mcp-server.md), [page](https://verifymcp.io/servers/cyanheads-nist-nvd-mcp-server/cyanheads-nist-nvd-mcp-server)

## Channel facts

- Endpoint: `https://nist-nvd.caseyjhand.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.0`

## 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-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 73/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 2153 tokens (~358/item across 6 items; 5 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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).

## Install

### How do I install the io.github.cyanheads/nist-nvd-mcp-server server?

io.github.cyanheads/nist-nvd-mcp-server is a hosted endpoint at https://nist-nvd.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-nist-nvd-mcp-server 'https://nist-nvd.caseyjhand.com/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  cyanheads-nist-nvd-mcp-server:
    url: "https://nist-nvd.caseyjhand.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "cyanheads-nist-nvd-mcp-server": {
      "type": "http",
      "url": "https://nist-nvd.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-10-26 (score 88, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “nvd_audit_cpe” rewrote its description, which is the text the model reads
- [security] Tool “nvd_get_cve” rewrote its description, which is the text the model reads
- [security] Tool “nvd_search_cves” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: 399 → 358
- [functional] First check of Schema quality: 100
- [functional] New resource “nist-nvd-guide”
- [functional] Server version: 0.3.2 → 0.4.0
- [cosmetic] “nvd_audit_cpe” added an optional parameter “includeConfigurations”
- [cosmetic] “nvd_audit_cpe” added an optional parameter “includeReferences”
- [cosmetic] “nvd_get_cve” added an optional parameter “includeConfigurations”
- [cosmetic] “nvd_audit_cpe” reworded the description of “limit”
- [cosmetic] “nvd_audit_cpe” reworded the description of “severityMin”
- [cosmetic] “nvd_get_cve” reworded the description of “cveIds”
- [cosmetic] “nvd_search_cpes” reworded the description of “limit”
- [cosmetic] “nvd_get_cve_history” reworded the description of “limit”
- [cosmetic] “nvd_search_cves” reworded the description of “limit”

### 2026-10-20 (score 86, 0)

- [security] Stability: 0.97 → pass

### 2026-10-19 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-12 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 73. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-10 (score 82, +2)

- [functional] Server version: 0.3.1 → 0.3.2

### 2026-10-06 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 53. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `nvd_get_cve` (~297 tokens)

Get CVE Details

Fetch one or more CVEs by ID from the NIST National Vulnerability Database. Returns CVSS scores across all available versions (v2.0, v3.0, v3.1, v4.0), CWE weakness classifications, affected CPE configurations, CISA KEV fields, current SSVC assessments, and references. Up to 100 CVE IDs per call. For bulk lookups of more than 10 IDs, use brief: true — full records for 100 CVEs can exceed 1MB and exhaust context budgets.

Input parameters:

- `allLanguages` (boolean): When true, keeps every localized description NVD supplies on each record, and full records render all of them. Default keeps English only, falling back to whatever exists if a record has no English e…
- `brief` (boolean): When true, returns trimmed records (ID, status, top CVSS score, KEV name, published date, and a truncated description) instead of full detail. Recommended for batches of more than 10 IDs.
- `cveIds` (required): One CVE ID or an array of CVE IDs; at most 100 are fetched per call.
- `includeConfigurations` (boolean): When false, omits configurationNodes from full records and their rendered text.
- `includeReferences` (boolean): When false, omits the references array to reduce response size.

Output parameters:

- `brief` (boolean): Whether brief or full records were returned.
- `cves` (array): CVE records — full detail by default, trimmed rows when brief is true.
- `effectiveLimit` (number): Page size or ID count used after clamping.
- `error` (object): Present when the call failed. Absent on success.
- `missingIds` (array): CVE IDs requested but not found in NVD. Absent when all IDs matched.
- `notice` (string): Explains when the requested ID count was clamped.
- `requested` (number): Number of CVE IDs processed in this call.
- `requestedLimit` (number): Requested page size or ID count before clamping.
- `returned` (number): Number of CVE records returned.
- `unprocessedIds` (array): IDs beyond the processed prefix, deduplicated in request order and excluding IDs already attempted.

### `nvd_search_cves` (~595 tokens)

Search CVEs

Search CVEs by keyword, severity, CWE, date range, or CISA KEV status. The primary discovery tool for vulnerability surveillance and triage workflows. pubDays and lastModDays expand to date pairs; values over 120 days are clamped to the NVD maximum and reported in the response enrichment. Returns brief summaries — call nvd_get_cve for full detail on specific IDs. At least one filter is recommended; omitting all filters returns CVEs in default NVD index order (oldest first by CVE ID). Blank string filters are omitted with a notice; nonblank strings are trimmed.

Input parameters:

- `cweId` (string): Filter by CWE weakness ID (e.g., "CWE-79", "NVD-CWE-Other").
- `exactPhrase` (boolean): When true, keyword matches as an exact phrase rather than ANDing its words independently. Requires keyword.
- `kevOnly` (boolean): When true, filters results to CVEs in the CISA Known Exploited Vulnerabilities catalog.
- `keyword` (string): Full-text search across CVE descriptions (AND-semantics across words).
- `lastModDays` (integer): CVEs last modified in the last N days (max 120; values over 120 are clamped). Mutually exclusive with lastModStartDate/lastModEndDate.
- `lastModEndDate` (string): ISO 8601 datetime for last-modified range end. Both required together.
- `lastModStartDate` (string): ISO 8601 datetime for last-modified range start. Both required together. Mutually exclusive with lastModDays.
- `limit` (integer): Maximum number of results to return (default 20; values above 2000 are clamped unless NVD_CLAMP_LIMITS is false).
- `noRejected` (boolean): When true (default), excludes CVEs with REJECT/Rejected status.
- `offset` (integer): Zero-based page offset for pagination.
- `pubDays` (integer): CVEs published in the last N days (max 120; values over 120 are clamped). Mutually exclusive with pubStartDate/pubEndDate.
- `pubEndDate` (string): ISO 8601 datetime for publication range end. Both pubStartDate and pubEndDate required together.
- `pubStartDate` (string): ISO 8601 datetime for publication range start. Both pubStartDate and pubEndDate required together. Mutually exclusive with pubDays.
- `severity` (string): Filter to CVEs in exactly this CVSS severity band — NVD matches the one band, not a floor. Covering several bands (e.g. HIGH and CRITICAL) takes one call per band.
- `severityVersion` (string): CVSS version to use for the severity filter. Default: v3 (maps to cvssV3Severity).

Output parameters:

- `cves` (array): Matching CVE summaries. Call nvd_get_cve for full detail on specific IDs.
- `datesClamped` (array): Entries for any pubDays/lastModDays values that exceeded 120 and were auto-clamped. Absent when no clamping occurred.
- `effectiveLimit` (number): Page size or ID count used after clamping.
- `error` (object): Present when the call failed. Absent on success.
- `filtersApplied` (object): The non-default filters this query actually applied — the ones that can account for an empty or unexpectedly narrow result set. Absent when the query ran unfiltered, which is itself the answer when a…
- `notice` (string): Ignored blank filters and paging guidance: distinguishes no matches, an exhausted offset, and an inconsistent empty upstream page; on a partial page, names the next offset.
- `offset` (number): Page offset used in this query.
- `requestedLimit` (number): Requested page size or ID count before clamping.
- `returned` (number): Number of CVEs returned in this response.
- `totalCount` (number): Total matching CVEs in NVD before pagination.

### `nvd_audit_cpe` (~489 tokens)

Audit CPE for Vulnerabilities

Find all CVEs affecting a specific product and version using CPE (Common Platform Enumeration). Requires either an exact CPE name (cpeName) or a partial match string (virtualMatchString) with optional version range bounds. With cpeName, NVD scopes results to configurations where the product is directly vulnerable, not merely referenced as a dependency. Use nvd_search_cpes first to resolve the correct CPE string for a product. Returns full CVE records including current SSVC assessments.

Input parameters:

- `allLanguages` (boolean): When true, keeps every localized description NVD supplies on each record. Default keeps English only.
- `cpeName` (string): Full CPEv2.3 name (e.g., "cpe:2.3:a:apache:http_server:2.4.51:*:*:*:*:*:*:*"). NVD adds isVulnerable automatically. Mutually exclusive with virtualMatchString.
- `includeConfigurations` (boolean): When false, omits configurationNodes from each record and its rendered text.
- `includeReferences` (boolean): When false, omits references from each record and its rendered text.
- `limit` (integer): Maximum number of CVEs to return (default 20; values above 2000 are clamped unless NVD_CLAMP_LIMITS is false).
- `offset` (integer): Zero-based page offset for pagination. Page through totalCount with a modest limit rather than raising limit — this tool returns full CVE records, so a large limit is a large response.
- `severityMin` (string): Keep CVEs whose highest severity band across all CVSS versions meets this threshold, which can exceed the row headline severity. Applied after NVD returns the page, so only CVEs within limit are eval…
- `versionEnd` (string): Upper version bound. Requires virtualMatchString.
- `versionEndType` (string): Whether the upper version bound is inclusive or exclusive.
- `versionStart` (string): Lower version bound. Requires virtualMatchString.
- `versionStartType` (string): Whether the lower version bound is inclusive or exclusive.
- `virtualMatchString` (string): Partial CPE match pattern (e.g., "cpe:2.3:a:apache:http_server:*"). Use with versionStart/versionEnd for version range audits. Mutually exclusive with cpeName.

Output parameters:

- `auditTarget` (string): The CPE name or virtual match string used for this audit.
- `cves` (array): Full CVE records for CVEs affecting the specified product.
- `effectiveLimit` (number): Page size or ID count used after clamping.
- `error` (object): Present when the call failed. Absent on success.
- `filteredCount` (number): CVEs below severityMin on every CVSS band, or with no scores, on the page NVD returned. Present whenever severityMin is set; 0 means none were dropped. Bands across all versions are evaluated indepen…
- `notice` (string): Guidance on the shape of this page. When no CVEs came back it distinguishes a target NVD holds no CVEs for from a severityMin filter that dropped everything on the page, from an offset past the resul…
- `offset` (number): Page offset used in this query.
- `requestedLimit` (number): Requested page size or ID count before clamping.
- `returned` (number): Number of CVE records returned.
- `severityMin` (string): The client-side minimum severity filter applied. Absent when none was set.
- `totalCount` (number): Total CVEs matched before pagination.

### `nvd_search_cpes` (~272 tokens)

Search CPE Dictionary

Search the NVD CPE (Common Platform Enumeration) dictionary by product keyword or partial match string. Returns CPE names, human-readable titles, and deprecation status. Use before nvd_audit_cpe to resolve the correct CPE name for a product — CPE strings are precise identifiers (e.g., cpe:2.3:a:apache:http_server:2.4.51:*:*:*:*:*:*:*) and must match exactly to audit the right product.

Input parameters:

- `cpeMatchString` (string): Partial CPEv2.3 pattern (e.g., "cpe:2.3:a:apache:http_server"). At least one of keyword or cpeMatchString is required.
- `keyword` (string): Product name or vendor keyword (e.g., "apache http server", "openssl", "nginx"). At least one of keyword or cpeMatchString is required.
- `limit` (integer): Maximum number of CPE entries to return (default 20; values above 10000 are clamped unless NVD_CLAMP_LIMITS is false).
- `offset` (integer): Zero-based page offset for pagination. When totalCount exceeds offset + returned, raise offset to reach the rest — a vendor-level keyword has nothing left to narrow toward.

Output parameters:

- `cpes` (array): Matching CPE dictionary entries.
- `effectiveLimit` (number): Page size or ID count used after clamping.
- `error` (object): Present when the call failed. Absent on success.
- `notice` (string): Guidance when no CPEs matched, the offset ran past the result set, NVD returned an empty page inside a range it says has matches, or entries remain beyond this page.
- `offset` (number): Page offset used in this query.
- `requestedLimit` (number): Requested page size or ID count before clamping.
- `returned` (number): Number of entries returned in this response.
- `totalCount` (number): Total matching CPE entries before the limit was applied.

### `nvd_get_cve_history` (~330 tokens)

Get CVE Change History

Retrieve the change history for a single CVE — CVSS score revisions, reference additions, status transitions (e.g., "Received" → "Analyzed"), and CPE configuration updates. Use when tracking a CVE's escalation or investigating when a score changed. Events are returned newest-first by default; pass order="oldest" for the CVE's earliest events. For the current record, call nvd_get_cve instead. The NVD history endpoint is significantly slower than other NVD endpoints, especially without an API key — set NVD_API_KEY for reliable operation.

Input parameters:

- `cveId` (string, required): CVE identifier to retrieve history for (e.g., "CVE-2021-44228").
- `limit` (integer): Maximum number of change events to return (default 20; values above 2000 are clamped unless NVD_CLAMP_LIMITS is false).
- `offset` (integer): Zero-based offset for paginating through change events, counted from whichever end order anchors to: offset 0 is the newest event under the default order="newest", and the oldest event under order="o…
- `order` (string): Which end of the history to page from. Default "newest" returns the most recent events first, which is what escalation and re-score questions need. "oldest" returns NVD's native order (the CVE's firs…

Output parameters:

- `changes` (array): CVE change events ordered to match the requested order — newest first by default, oldest first when order="oldest".
- `cveId` (string): The CVE ID for which history was retrieved.
- `effectiveLimit` (number): Page size or ID count used after clamping.
- `error` (object): Present when the call failed. Absent on success.
- `notice` (string): Guidance on the shape of this page. When no events came back it distinguishes an offset past the end of the history, from an empty page NVD returned inside a range it says has events, from a CVE NVD…
- `offset` (number): Page offset used in this query.
- `order` (string): Which end of the history this page was anchored to.
- `requestedLimit` (number): Requested page size or ID count before clamping.
- `returned` (number): Number of change events returned in this response.
- `totalCount` (number): Total change events on record for this CVE.

## Diagnostics

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

## Score history

- 2026-11-05: 88
- 2026-11-04: 88
- 2026-11-03: 88
- 2026-11-02: 88
- 2026-11-01: 88
- 2026-10-31: 88
- 2026-10-30: 88
- 2026-10-29: 88
- 2026-10-28: 88
- 2026-10-27: 88
- 2026-10-26: 88
- 2026-10-25: 86
- 2026-10-24: 86
- 2026-10-23: 86
- 2026-10-22: 86
- 2026-10-21: 86
- 2026-10-20: 86
- 2026-10-19: 86
- 2026-10-18: 85
- 2026-10-17: 85
- 2026-10-16: 85
- 2026-10-15: 84
- 2026-10-14: 84
- 2026-10-13: 83
- 2026-10-12: 83
- 2026-10-10: 82
- 2026-10-06: 80
- 2026-10-04: 79
- 2026-10-03: 78
- 2026-10-02: 78

## Common questions

### What is the io.github.cyanheads/nist-nvd-mcp-server server?

io.github.cyanheads/nist-nvd-mcp-server is listed in the public MCP registry as io.github.cyanheads/nist-nvd-mcp-server. Search and audit NIST NVD CVEs by keyword, severity, CWE, CISA KEV status, and CPE. This page covers its hosted endpoint (https://nist-nvd.caseyjhand.com/mcp).

### Is the io.github.cyanheads/nist-nvd-mcp-server server safe to use?

io.github.cyanheads/nist-nvd-mcp-server scores 88 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/nist-nvd-mcp-server server expose?

io.github.cyanheads/nist-nvd-mcp-server exposes 5 tools: nvd_get_cve, nvd_search_cves, nvd_audit_cpe, nvd_search_cpes, nvd_get_cve_history. Their descriptions and schemas cost roughly 1,983 tokens of context every time the server is loaded.

### Does the io.github.cyanheads/nist-nvd-mcp-server server require authentication?

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

### Is the io.github.cyanheads/nist-nvd-mcp-server server still maintained?

io.github.cyanheads/nist-nvd-mcp-server is still listed as active in the MCP registry. We last reached this channel on 5 November 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://nist-nvd.caseyjhand.com/mcp
- Repository: https://github.com/cyanheads/nist-nvd-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/cyanheads-nist-nvd-mcp-server/nist-nvd.xml
- Changelog JSON feed: https://verifymcp.io/servers/cyanheads-nist-nvd-mcp-server/nist-nvd.json
- HTML version of this page: https://verifymcp.io/servers/cyanheads-nist-nvd-mcp-server/nist-nvd