Search and audit NIST NVD CVEs by keyword, severity, CWE, CISA KEV status, and CPE.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag β we're steadily working through the catalog.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Search and audit CVEs by keyword, severity, CWE, CISA KEV status, and CPE via the NIST National Vulnerability Database. STDIO or Streamable HTTP.
Public Hosted Server: https://nist-nvd.caseyjhand.com/mcp
Five tools for vulnerability research, CPE auditing, and change tracking against the NIST NVD API 2.0:
| Tool | Description |
|---|---|
nvd_search_cves | Search CVEs by keyword, severity, CWE, date range, or CISA KEV status. |
nvd_get_cve | Fetch one or more CVEs by ID β full CVSS scores, CWE, CPE configs, KEV fields, and references. |
nvd_search_cpes | Search the NVD CPE dictionary by product keyword or partial match string. |
nvd_audit_cpe | Find all CVEs affecting a specific product version by CPE name or virtual match string. |
nvd_get_cve_history | Retrieve the change history for a CVE β score revisions, status transitions, and reference additions. |
nvd_search_cvesThe primary discovery tool for vulnerability surveillance and triage workflows.
exactPhrase: true to match the keyword as a phraseCWE-79, NVD-CWE-Other)pubDays and lastModDays for "last N days" queriespubStartDate/pubEndDate, etc.) with 120-day max spanlimit (up to 2000) and offsetnvd_get_cve for full detailnvd_get_cveFetch one or more CVEs by ID with full detail or brief summaries.
brief: true): ID, status, top severity, KEV name, truncated description β recommended for batches larger than 10includeReferences: false to strip the references array and reduce response sizemissingIds enrichment field lists any requested IDs NVD didn't returnβ¦ N more trailer; allLanguages: true renders every localized description, not just Englishnvd_search_cpesLook up product identifiers before auditing.
"apache http server", "openssl") or partial CPEv2.3 patternlimit (up to 10,000 per page) and offset β a vendor-level keyword can match tens of thousands of entries, so page with offset rather than trying to narrow furthernvd_audit_cpe β CPE names are arcane strings; guessing audits the wrong productnvd_audit_cpeFull CVE audit for a specific product version.
cpeName (NVD auto-applies isVulnerable) or virtualMatchString with optional version range boundsversionStart/versionEnd with inclusive/exclusive type controlseverityMin) to strip low-signal entrieslimit (up to 2000) and offset β page at a modest limit instead of raising it, since each result is a full recordnvd_get_cve_historyTrack a CVE's lifecycle over time.
order picks which end to read from β newest (default) returns the most recent events first, oldest returns NVD's native oldest-first orderlimit and offset, where offset counts from the end order anchors toNVD_API_KEY and raise NVD_REQUEST_TIMEOUT_MS for reliable operation| Type | Name | Description |
|---|---|---|
| Resource | nvd://cve/{cveId} | Full CVE record by ID β same data as nvd_get_cve for a single ID, as a stable URI for injectable context. |
All resource data is also reachable via tools.
Built on @cyanheads/mcp-ts-core:
none, jwt, oauthin-memory, filesystem, Supabase, Cloudflare KV/R2/D1NVD-specific:
Retry-After holds the whole queue until NVD's window resets. Keyless, a 403 fails fast and names NVD_API_KEY rather than spending a 5-request budget on retries that cannot outlast a 30-second windowmessage header β a refused key surfaces as a config fault naming NVD_API_KEY rather than as a malformed CVE IDAgent-friendly output:
enrichment block on every response, carried on both structuredContent and the rendered text β total results, returned count, page offset, the filters actually applied, and any date-clamping events, so agents can reason about what was really queriedmissingIds in batch CVE lookups β per-ID parity check instead of a silent partial resultcpeName or virtualMatchString reflected back so callers can verify the correct product was auditedtotalCount: 0 on either input arm, so "no known vulnerabilities" reads as the answer it isAdd the following to your MCP client configuration file.
Or with npx (no Bun required):
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/nist-nvd-mcp-server)<a href="https://allmcps.com/mcp/nist-nvd-mcp-server"><img src="https://allmcps.com/api/badge/nist-nvd-mcp-server?style=directory" alt="Nist Nvd MCP Server on AllMCPs" /></a>