Is an API Key mandatory?

No. The NVD API allows public access without a key. However, using a key increases your rate limit significantly (up to 50 requests per 30 seconds).

What is a CPE string?

CPE (Common Platform Enumeration) is a structured naming scheme for information technology systems, software, and packages (e.g., cpe:2.3:a:microsoft:exchange_server:2019).

How far back can I search for vulnerabilities?

The NVD contains vulnerabilities dating back to the late 1990s. You can search the entire database by ID or keyword.

NIST NVD MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: NIST NVD
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install NIST NVD and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "nist-nvd": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About NIST NVD MCP Server

Connect to the National Vulnerability Database (NVD) API through your AI agent and explore the world's most comprehensive archive of cybersecurity vulnerabilities and product data using natural conversation.

GitHub Copilot Agent mode brings NIST NVD data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools — Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

CVE Discovery — Search for Common Vulnerabilities and Exposures (CVEs) by ID, keyword, or specific weakness (CWE).
Product Security — Find all vulnerabilities associated with a specific product or version using its Common Platform Enumeration (CPE) string.
Severity Analysis — Filter vulnerabilities based on their CVSS V3 severity level (Low to Critical) to prioritize risks.
Temporal Tracking — Search for CVEs published or modified within specific date ranges to monitor recent threats.
Product Dictionary — Query the official CPE dictionary by keyword or UUID to identify software and hardware products.
Change History — Retrieve a detailed log of updates and modifications made to the vulnerability database.

The NIST NVD MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect NIST NVD to VS Code Copilot via MCP

Follow these steps to integrate the NIST NVD MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using NIST NVD

Ask Copilot: "Using NIST NVD, help me..." — 10 tools available

Why Use VS Code Copilot with the NIST NVD MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with NIST NVD through the Model Context Protocol.

VS Code is used by over 70% of developers — adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

NIST NVD + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the NIST NVD MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

NIST NVD MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect NIST NVD to VS Code Copilot via MCP:

get_cpe_by_id

Get CPE dictionary entry by UUID

get_cve_by_id

g. CVE-2023-1234). Get CVE details by ID

get_cve_change_history

Retrieve CVE change history

list_cpe_matches

List valid CPE match strings

search_cpe_by_keyword

Search product dictionary by keyword

search_cve_by_cpe

Find CVEs for a product (CPE)

search_cve_by_cwe

g. CWE-89). Find CVEs by weakness (CWE)

search_cve_by_date

Search CVEs by publication date

search_cve_by_keyword

Search CVEs by keyword

search_cve_by_severity

Filter CVEs by severity

Example Prompts for NIST NVD in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with NIST NVD immediately.

"Get the details for CVE-2023-23397."

"Search for vulnerabilities in 'WordPress' with CRITICAL severity."

"What is the official CPE name for 'Windows 11'?"

Troubleshooting NIST NVD MCP Server with VS Code Copilot

Common issues when connecting NIST NVD to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

NIST NVD + VS Code Copilot FAQ

Common questions about integrating NIST NVD MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.