Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.cyanheads/nist-nvd-mcp-server

REMOTE · NIST-NVD.CASEYJHAND.COM · 2 COMPONENTS

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

0 this week 88 Trust /100

Last scanned (5 hours ago)

Scores higher than 96% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Security

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security83
Transport & Reachability100
Schema Quality & AI Usability73
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 26 Oct 26 +2
    • 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 security
    • 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 functional
    • “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” cosmetic
  • 20 Oct 26 0
    • Stability: 0.97 → pass security
  • 19 Oct 26 +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.

  • 16 Oct 26 +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.

  • 14 Oct 26 +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.

  • 12 Oct 26 +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.

  • 10 Oct 26 +2
    • Server version: 0.3.1 → 0.3.2 functional
  • 6 Oct 26 +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.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://nist-nvd.caseyjhand.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=caseyjhand.com CN=WE1,O=Google Trust Services,C=US 2 Nov 2026 31 Jan 2027 ECDSA 256 ECDSA-SHA256 995a30681ab772540e934241ca1d576c
SANs: caseyjhand.com, *.caseyjhand.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of nist-nvd.caseyjhand.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
caseyjhand.com. present 2371 13 Verified
nist-nvd.caseyjhand.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://nist-nvd.caseyjhand.com/mcp Verified 200
http (plaintext) http://nist-nvd.caseyjhand.com/mcp HTTPS enforced 301 https://nist-nvd.caseyjhand.com/mcp
MCP tools · 5 exposed · ~1,983 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
nvd_audit_cpe ~489

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.

NameTypeReqDescription
allLanguagesboolean–When true, keeps every localized description NVD supplies on each record. Default keeps English only.
cpeNamestring–Full CPEv2.3 name (e.g., "cpe:2.3:a:apache:http_server:2.4.51:*:*:*:*:*:*:*"). NVD adds isVulnerable automatically. Mutually exclusive with virtualMatchString.
includeConfigurationsboolean–When false, omits configurationNodes from each record and its rendered text.
includeReferencesboolean–When false, omits references from each record and its rendered text.
limitinteger–Maximum number of CVEs to return (default 20; values above 2000 are clamped unless NVD_CLAMP_LIMITS is false).
offsetinteger–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.
severityMinstring–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…
versionEndstring–Upper version bound. Requires virtualMatchString.
versionEndTypestring–Whether the upper version bound is inclusive or exclusive.
versionStartstring–Lower version bound. Requires virtualMatchString.
versionStartTypestring–Whether the lower version bound is inclusive or exclusive.
virtualMatchStringstring–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.
NameTypeReqDescription
auditTargetstring–The CPE name or virtual match string used for this audit.
cvesarray–Full CVE records for CVEs affecting the specified product.
effectiveLimitnumber–Page size or ID count used after clamping.
errorobject–Present when the call failed. Absent on success.
filteredCountnumber–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…
noticestring–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…
offsetnumber–Page offset used in this query.
requestedLimitnumber–Requested page size or ID count before clamping.
returnednumber–Number of CVE records returned.
severityMinstring–The client-side minimum severity filter applied. Absent when none was set.
totalCountnumber–Total CVEs matched before pagination.

No examples provided.

nvd_get_cve ~297

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.

NameTypeReqDescription
allLanguagesboolean–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…
briefboolean–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–yesOne CVE ID or an array of CVE IDs; at most 100 are fetched per call.
includeConfigurationsboolean–When false, omits configurationNodes from full records and their rendered text.
includeReferencesboolean–When false, omits the references array to reduce response size.
NameTypeReqDescription
briefboolean–Whether brief or full records were returned.
cvesarray–CVE records — full detail by default, trimmed rows when brief is true.
effectiveLimitnumber–Page size or ID count used after clamping.
errorobject–Present when the call failed. Absent on success.
missingIdsarray–CVE IDs requested but not found in NVD. Absent when all IDs matched.
noticestring–Explains when the requested ID count was clamped.
requestednumber–Number of CVE IDs processed in this call.
requestedLimitnumber–Requested page size or ID count before clamping.
returnednumber–Number of CVE records returned.
unprocessedIdsarray–IDs beyond the processed prefix, deduplicated in request order and excluding IDs already attempted.

No examples provided.

nvd_get_cve_history ~330

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.

NameTypeReqDescription
cveIdstringyesCVE identifier to retrieve history for (e.g., "CVE-2021-44228").
limitinteger–Maximum number of change events to return (default 20; values above 2000 are clamped unless NVD_CLAMP_LIMITS is false).
offsetinteger–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…
orderstring–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…
NameTypeReqDescription
changesarray–CVE change events ordered to match the requested order — newest first by default, oldest first when order="oldest".
cveIdstring–The CVE ID for which history was retrieved.
effectiveLimitnumber–Page size or ID count used after clamping.
errorobject–Present when the call failed. Absent on success.
noticestring–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…
offsetnumber–Page offset used in this query.
orderstring–Which end of the history this page was anchored to.
requestedLimitnumber–Requested page size or ID count before clamping.
returnednumber–Number of change events returned in this response.
totalCountnumber–Total change events on record for this CVE.

No examples provided.

nvd_search_cpes ~272

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.

NameTypeReqDescription
cpeMatchStringstring–Partial CPEv2.3 pattern (e.g., "cpe:2.3:a:apache:http_server"). At least one of keyword or cpeMatchString is required.
keywordstring–Product name or vendor keyword (e.g., "apache http server", "openssl", "nginx"). At least one of keyword or cpeMatchString is required.
limitinteger–Maximum number of CPE entries to return (default 20; values above 10000 are clamped unless NVD_CLAMP_LIMITS is false).
offsetinteger–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.
NameTypeReqDescription
cpesarray–Matching CPE dictionary entries.
effectiveLimitnumber–Page size or ID count used after clamping.
errorobject–Present when the call failed. Absent on success.
noticestring–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.
offsetnumber–Page offset used in this query.
requestedLimitnumber–Requested page size or ID count before clamping.
returnednumber–Number of entries returned in this response.
totalCountnumber–Total matching CPE entries before the limit was applied.

No examples provided.

nvd_search_cves ~595

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.

NameTypeReqDescription
cweIdstring–Filter by CWE weakness ID (e.g., "CWE-79", "NVD-CWE-Other").
exactPhraseboolean–When true, keyword matches as an exact phrase rather than ANDing its words independently. Requires keyword.
kevOnlyboolean–When true, filters results to CVEs in the CISA Known Exploited Vulnerabilities catalog.
keywordstring–Full-text search across CVE descriptions (AND-semantics across words).
lastModDaysinteger–CVEs last modified in the last N days (max 120; values over 120 are clamped). Mutually exclusive with lastModStartDate/lastModEndDate.
lastModEndDatestring–ISO 8601 datetime for last-modified range end. Both required together.
lastModStartDatestring–ISO 8601 datetime for last-modified range start. Both required together. Mutually exclusive with lastModDays.
limitinteger–Maximum number of results to return (default 20; values above 2000 are clamped unless NVD_CLAMP_LIMITS is false).
noRejectedboolean–When true (default), excludes CVEs with REJECT/Rejected status.
offsetinteger–Zero-based page offset for pagination.
pubDaysinteger–CVEs published in the last N days (max 120; values over 120 are clamped). Mutually exclusive with pubStartDate/pubEndDate.
pubEndDatestring–ISO 8601 datetime for publication range end. Both pubStartDate and pubEndDate required together.
pubStartDatestring–ISO 8601 datetime for publication range start. Both pubStartDate and pubEndDate required together. Mutually exclusive with pubDays.
severitystring–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.
severityVersionstring–CVSS version to use for the severity filter. Default: v3 (maps to cvssV3Severity).
NameTypeReqDescription
cvesarray–Matching CVE summaries. Call nvd_get_cve for full detail on specific IDs.
datesClampedarray–Entries for any pubDays/lastModDays values that exceeded 120 and were auto-clamped. Absent when no clamping occurred.
effectiveLimitnumber–Page size or ID count used after clamping.
errorobject–Present when the call failed. Absent on success.
filtersAppliedobject–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…
noticestring–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.
offsetnumber–Page offset used in this query.
requestedLimitnumber–Requested page size or ID count before clamping.
returnednumber–Number of CVEs returned in this response.
totalCountnumber–Total matching CVEs in NVD before pagination.

No examples provided.

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.

remote · nist-nvd.caseyjhand.com

# add to Claude Code
claude mcp add --transport http cyanheads-nist-nvd-mcp-server 'https://nist-nvd.caseyjhand.com/mcp'
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.