NVD Database MCP Server

Queries the NIST National Vulnerability Database (NVD) via its API.

Local serverstdioPython 14

What is the NVD Database MCP server?

Connect NVD Database to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Queries the NIST National Vulnerability Database (NVD) via its API. The nvd database mcp server is what makes that connection.

What the server does

As a prerequisite an NVD API key is required. (Request here).

  • Query specific CVEs by ID with detailed vulnerability data
  • Search the NVD database by keyword with customizable result options
  • Supports Server-Sent Events (SSE) transport for real-time communication
  • Compatible with MCP-compliant clients like Claude Desktop

Installation

Installation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Description — Retrieves a CVE record by its ID
  • Parameters — - cve_id (str): The CVE ID (e.g., CVE-2019-1010218)
  • Returns — Detailed CVE info including scores, weaknesses, and references
  • Note — Assumes test_tools.py is copied into the image at /app/tests/. If not, modify the Dockerfile to include:
  • Tools — The server implements the following tools to query the NVD Database:
  • Setup — 2. Clone the Repository: bash git clone https://github.com/marcoeg/mcp-nvd cd mcp-nvd
  • Build — The Build tool exposed by this server
  • Verify — The Verify tool exposed by this server
  • Notes — Here’s the summary formatted as Markdown comments within a code block, suitable for inclusion in a file like docker-compose.yaml or README.md:
  • Assumptions — The Assumptions tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: NVD_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch NVD Database.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. NVD Database's toolset — Description, Parameters, Returns and 7 more — is a fair guide to whether it matches your workflow. It is maintained by marcoeg; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against NVD Database's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
DescriptionRetrieves a CVE record by its ID.
Parameters- cve_id (str): The CVE ID (e.g., CVE-2019-1010218).
ReturnsDetailed CVE info including scores, weaknesses, and references.
NoteAssumes test_tools.py is copied into the image at /app/tests/. If not, modify the Dockerfile to include:
ToolsThe server implements the following tools to query the NVD Database:
Setup2. **Clone the Repository**: bash git clone https://github.com/marcoeg/mcp-nvd cd mcp-nvd
BuildThe Build tool exposed by this server.
VerifyThe Verify tool exposed by this server.
NotesHere’s the summary formatted as Markdown comments within a code block, suitable for inclusion in a file like docker-compose.yaml or README.md:
AssumptionsThe Assumptions tool exposed by this server.

How to install the NVD Database MCP server

{
  "mcpServers": {
    "mcp-nvd": {
      "command": "/path/to/uvx",
      "args": ["mcp-nvd"],
      "env": {
        "NVD_API_KEY": "your-api-key"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
NVD_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use NVD Database to Description.
  • Use NVD Database to Parameters.
  • Use NVD Database to Returns.

Frequently asked questions

You can search for specific CVEs by ID, search the database using keywords, get detailed vulnerability information including scores and references, and receive real-time updates via SSE.