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

io.github.cyanheads/nist-nvd-mcp-server · v0.3.2 · security

io.github.cyanheads/nist-nvd-mcp-server is healthy: it completed an MCP handshake in 214 ms and exposes 5 tools.

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

Endpoint: https://nist-nvd.caseyjhand.com/mcp (streamable-http)

Repository · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count5
Latency214 ms
Last checked (UTC)2026-10-16T07:20:34.597Z

Health history

Checked (UTC)StatusLatencyError
2026-10-16T07:20:34.597ZHealthy214
2026-10-15T03:25:40.560ZHealthy2839

Tools (5)

nvd_get_cveFetch 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, and references. Up to 100 CVE IDs per call. For bulk lookups of more tha
nvd_search_cvesSearch CVEs by keyword, severity, CWE, date range, or CISA KEV status. The primary discovery tool for vulnerability surveillance and triage workflows. pubDays and lastModDays are convenience shorthands that expand to date pairs; values over 120 days are clamped to the NVD maximum and reported in the
nvd_audit_cpeFind 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 direc
nvd_search_cpesSearch 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:apac
nvd_get_cve_historyRetrieve 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 o