Summary
Scoped tightly to the triage question: what is this CVE ID, and what is on record against this product name.
There is no asset inventory, no scanning and no remediation guidance here — get_cve_details returns the NVD record for an ID and search_cves finds records by keyword, which is enough to settle an advisory mid-conversation and not enough to run a vulnerability programme. search_cves is narrowed by keyword and capped by limit with no vendor, severity or date filter in the call, so a broad product keyword is a blunt instrument and a specific one is the way to use it.
What it is
A server over NVD CVE records exposing lookup by CVE ID and keyword search across vulnerability descriptions, product names and vendors.
What you get
- Lookup by identifier: get_cve_details takes a cve_id and returns that record's description, CVSS score, severity and reference links.
- Search for when you have a name and not an ID: search_cves matches a keyword against vulnerability descriptions, product names and vendors, with limit capping how many come back.
Requirements
Nothing — no account, no key.
Setup effort
One command — npx -y nvd-cve-mcp-server