nist-nvd-mcp-server
io.github.cyanheads/nist-nvd-mcp-servercyanheadsstreamable-httpv0.4.1Scanned
Search and audit NIST NVD CVEs by keyword, severity, CWE, CISA KEV status, and CPE.
5 tools: 5 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the nist-nvd-mcp-server can do
The nist-nvd-mcp-server is published by the GitHub account cyanheads. It has 5 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
1 tool reads private data (nvd_get_cve).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 16, 2026, version 0.4.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Only reads 5Show 5 read-only tools
nvd_audit_cpeFind all CVEs affecting a specific product and version using CPE (Common Platform Enumeration).No findings
Why it is in this group
- The description's first verb is "find": a word for reading.
Description, as the server wrote it 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. Narrow the audit server-side with kevOnly, an exact severity band, or publication, last-modified, or KEV-addition date windows; pubDays, lastModDays, and kevDays expand to date pairs ending at call time, values over 120 days are clamped and reported, and a shorthand re-expands on every call, so page with the dates echoed in filtersApplied. Returns full CVE records including current SSVC assessments, each score's supplier, and the affected products the CNA and any ADP state themselves.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
nvd_get_cveFetch one or more CVEs by ID from the NIST National Vulnerability Database.Reads private dataNo findings
Why it is in this group
- The name "nvd_get_cve" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "fetch" and "database": it reads databases.
Description, as the server wrote it 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) with who supplied each, CWE weakness classifications, affected CPE configurations from NVD analysis, the affected products the CNA and any ADP state themselves, the record's source and tags, CISA KEV fields, current SSVC assessments, and references. Up to 100 distinct 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
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.No findings
Why it is in this group
- The name "nvd_get_cve_history" says "get": a word for reading.
Description, as the server wrote it 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 on a server running without an API key (a server operator sets NVD_API_KEY).
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
nvd_search_cpesSearch the NVD CPE (Common Platform Enumeration) dictionary by product keyword or partial match string.No findings
Why it is in this group
- The name "nvd_search_cpes" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
nvd_search_cvesSearch CVEs by keyword, severity, CWE, publication or last-modified date, CISA KEV status, or the date CISA added a CVE to KEV.No findings
Why it is in this group
- The name "nvd_search_cves" says "search": a word for reading.
Description, as the server wrote it Search CVEs by keyword, severity, CWE, publication or last-modified date, CISA KEV status, or the date CISA added a CVE to KEV. The primary discovery tool for vulnerability surveillance and triage workflows. pubDays, lastModDays, and kevDays expand to date pairs ending at call time; values over 120 days are clamped to the NVD maximum and reported in the response enrichment. A shorthand re-expands on every call, so page with the dates echoed in filtersApplied. 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:32 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools4 changed.~4 changedView diff
- Changed:nvd_audit_cpeOnly readsdescriptioninputSchema
- Changed:nvd_get_cveOnly readsdescriptioninputSchema
- Changed:nvd_get_cve_historyOnly readsdescription
- Changed:nvd_search_cvesOnly readsdescriptioninputSchema
Tools5 changed.~5 changedView diff
- Changed:nvd_audit_cpeOnly readsdescriptioninputSchema
- Changed:nvd_get_cveOnly readsdescriptioninputSchema
- Changed:nvd_get_cve_historyOnly readsinputSchema
- Changed:nvd_search_cpesOnly readsinputSchema
- Changed:nvd_search_cvesOnly readsdescriptioninputSchema
Install
Pinned to version 0.4.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http nist-nvd https://nist-nvd.caseyjhand.com/mcpclaude mcp add --transport http nist-nvd https://nist-nvd.caseyjhand.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__nist-nvd__nvd_get_cve",
"mcp__nist-nvd__nvd_search_cves",
"mcp__nist-nvd__nvd_audit_cpe",
"mcp__nist-nvd__nvd_search_cpes",
"mcp__nist-nvd__nvd_get_cve_history"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as nist-nvd. Review it before you use it.
Capability tags behind 1 rule
- mcp__nist-nvd__nvd_get_cve private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.cyanheads/nist-nvd-mcp-server/verify?hash=421c5e06548553d2ad2b83a492d0eb6dd10ebb945fd7206ba83c9ee5ac951dca" | jq -e '.changed == false'Pinned hash 421c5e065485, from Nov 16, 2026, 07:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.cyanheads/nist-nvd-mcp-server/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.cyanheads/nist-nvd-mcp-server)Source: MCP Registry · repository. Synced Nov 16, 2026, 07:17 UTC.
nist-nvd-mcp-server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the nist-nvd-mcp-server safe?
- No scan can promise that. What its definitions show: 5 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the nist-nvd-mcp-server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the nist-nvd-mcp-server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the nist-nvd-mcp-server have?
- 5 tools: 5 read. nvd_get_cve, nvd_search_cves, nvd_audit_cpe, nvd_search_cpes and nvd_get_cve_history.
Does the nist-nvd-mcp-server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the nist-nvd-mcp-server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the nist-nvd-mcp-server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.