NIST NVD MCP. Correlate CVEs and CPE data across any search dimension.

You're connecting your AI agent straight to the National Vulnerability Database (NVD). This means you get direct access to the most authoritative cybersecurity data out there—no need to piece together risk reports from half a dozen different sources. You can track specific CVE IDs, map product weaknesses using CPE strings, or search for vulnerabilities based on severity and date.

We're talking deep intelligence, pulled through your AI client.

When you need details about one specific vulnerability, use get_cve_by_id. Just give it the unique CVE identifier (like CVE-2023-1234), and you get every single detail on that weakness. If you're looking at a product, you can find all associated vulnerabilities using its CPE string; just run search_cve_by_cpe. You also wanna know what changed? Use get_cve_change_history to pull a log of every update or modification made to the vulnerability database—perfect for tracking data changes over time.

If you're starting from product information, you can first look up its full dictionary entry using its specific UUID via get_cpe_by_id. You wanna know what products exist? Use search_cpe_by_keyword to search the product dictionary with a general term, helping you spot potential software or hardware targets. To see all possible scope definitions for filtering, run list_cpe_matches which lists every valid CPE match string available in the dictionary.

Filtering and Searching by Weakness: When you're hunting for vulnerabilities based on risk, use search_cve_by_severity. This lets you filter the entire pool of issues down to only show weaknesses above a certain threshold—think 'Critical' or 'High.' If the weakness isn't tied to a specific product, you can target it by common weakness type (CWE) using search_cve_by_cwe.

You also don't need product names for broad searches; run search_cve_by_keyword to perform a general search across the database using terms like 'SQL injection' or 'Remote Code Execution.'

Pinpointing Threats in Time and Scope: To focus on when things happened, use search_cve_by_date. You just give it a date range, and you get all CVEs published or modified within that specific window. For the deepest dive into product weakness, combine your knowledge: if you know both the CPE string and want to see associated weaknesses, run search_cve_by_cpe again.

If you need to narrow down a search using general terms but also link it to an existing product identifier, you can use search_cve_by_keyword on the CVE side.

The bottom line is this: This setup lets your agent handle complex queries that would otherwise take hours of manual API calls. You don't need to know NVD's internal structure—you just tell it what you want. Whether you're checking for all weaknesses associated with 'Windows Server 2019,' tracking every change made to the database last week, or looking up general product details using CPE keywords, this gives you a direct line to industry-standard risk data.