# NIST NVD MCP for AI Agents AI Agent Connect

> NIST NVD MCP lets you pull official vulnerability data directly into your AI agent. Stop manually browsing the National Vulnerability Database to hunt for flaws. You can query CVEs by ID or keyword, check product security via CPE strings, and filter by severity or date to build accurate threat intelligence on the fly. It gives your agent the data it needs to perform risk assessments without the manual research.

## Overview
- **Category:** the-unthinkable
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_di1FzaR2p54s3bOkX9Kq05itOme6MTw3QnOWExLr/ai-agent-connect
- **Tags:** cve, cybersecurity, vulnerability-management, threat-intelligence, security-standards, product-security

## Description

NIST NVD MCP connects your AI client to the National Vulnerability Database, the go-to source for cybersecurity flaws. Instead of jumping between browser tabs to copy-paste CVE details, you can just ask your agent to find specific risks. It handles the heavy lifting of querying the database for known vulnerabilities, severity scores, and product-specific security history. Whether you're hunting for a specific weakness like a buffer overflow or trying to see if a piece of hardware is compromised, this tool gives your agent the data it needs to give you straight answers. It's part of the Vinkius catalog, which makes it easy to plug into your existing workflow without worrying about the underlying API complexity. You get authoritative data on what's broken in the world right where you're already working. You can ask it to find every high-severity flaw for a specific version of a web server or pull the history of a known bug to see how its status has changed. This isn't just a list of links; it's a way to turn the NVD into a searchable knowledge base for your agent. You can quickly cross-reference multiple products against known threats or check if a new software release has any outstanding issues. It takes the friction out of security research by putting the data in your chat window.

## Tools

### search_cpe_by_keyword
Find specific software or hardware products using a simple keyword search in the dictionary.

### search_cve_by_cpe
Identify all vulnerabilities associated with a specific product or version string.

### search_cve_by_cwe
Find flaws based on the specific type of weakness like SQL injection or buffer overflows.

### search_cve_by_date
Filter the database for vulnerabilities published or modified during a specific timeframe.

### search_cve_by_keyword
Search for CVEs using general terms or specific vulnerability descriptions.

### search_cve_by_severity
Filter results to only show vulnerabilities with specific CVSS severity levels.

### get_cpe_by_id
Retrieve the specific product entry from the CPE dictionary using its unique UUID.

### get_cve_change_history
See the timeline of updates and modifications for a specific vulnerability record.

### list_cpe_matches
Get a list of valid CPE strings that match your specific product search terms.

### get_cve_by_id
Pull the full details for a specific vulnerability record using its CVE identifier.

## Prompt Examples

**Prompt:** 
```
Are there any critical vulnerabilities for Windows 11?
```

**Response:** 
```
I've checked the NVD for Windows 11. There are several critical vulnerabilities currently listed. The most recent ones involve **Elevation of Privilege**. 

Would you like me to list the specific CVE IDs or show you the severity scores?
```

**Prompt:** 
```
Find me all CVEs related to SQL injection from last year.
```

**Response:** 
```
Searching for SQL injection weaknesses (CWE-89) published in 2023... I found 142 records. Here are the top 5 most recent ones:

| CVE ID | Severity | Date |
|---|---|---|
| CVE-2023-XXXX | Critical | 2023-11-12 |
| CVE-2023-YYYY | High | 2023-10-05 |
```

**Prompt:** 
```
What's the official CPE for 'Google Chrome'?
```

**Response:** 
```
The official CPE dictionary entry for Google Chrome is `cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*`. I can also find specific versions if you need to narrow down the search for vulnerabilities.
```

## Capabilities

### Search vulnerabilities by weakness type
Find all CVEs related to specific issues like SQL injection or buffer overflows using CWE codes.

### Identify risks for specific products
Link vulnerabilities to specific hardware or software versions using official CPE strings.

### Filter by severity levels
Isolate critical and high-risk threats to prioritize your security response.

### Track vulnerability history
View the timeline of updates and modifications for any specific CVE record.

### Query the product dictionary
Search for official product identifiers using simple keywords or unique UUIDs.

### Filter by publication date
Monitor recent threats by searching for vulnerabilities modified within specific timeframes.

## Use Cases

### Identifying risks for a specific router
A user asks the agent to find CVEs for a specific CPE string. The agent uses search_cve_by_cpe to return a list of active threats for that hardware.

### Finding high-severity flaws in a recent update
A developer asks for all 'Critical' vulnerabilities published in the last month. The agent uses search_cve_by_severity and search_cve_by_date to provide the list.

### Researching specific weakness types
A researcher wants to see all flaws related to Cross-Site Scripting. The agent uses search_cve_by_cwe to pull all relevant records from the NVD.

### Auditing vulnerability change logs
A compliance officer needs the history of changes for a known bug. The agent uses get_cve_change_history to pull the full timeline of modifications.

## Benefits

- Stop manual searching by using search_cpe_by_keyword to find products instantly.
- Prioritize your fix list by filtering results with search_cve_by_severity to focus on critical risks.
- Map flaws to specific hardware using search_cve_by_cpe to see what's actually at risk in your stack.
- Track how threats evolve using get_cve_change_history to see recent database updates.
- Identify specific weaknesses quickly with search_cve_by_cwe to group similar risks by type.

## How It Works

The bottom line is you get a direct line to authoritative vulnerability data without the manual searching.

1. Subscribe to the NIST NVD MCP on Vinkius.
2. Add your NIST NVD API Key to your configuration to increase your rate limits.
3. Ask your agent to look up CVE details, product CPEs, or security history.

## Frequently Asked Questions

**Can the NIST NVD MCP help me identify which products are at risk?**
Yes, it allows your agent to search for specific hardware and software products using keywords or official identifiers to see exactly what vulnerabilities apply to them.

**How does the NIST NVD MCP handle different security severity levels?**
You can ask your agent to filter results by CVSS scores, letting you focus only on the most critical threats that need immediate attention.

**Can I use the NIST NVD MCP to track changes to a specific vulnerability?**
Yes, the Connector can pull the full change history for a CVE, showing you how the database record has been updated over time.

**Is the NIST NVD MCP good for security audits?**
It's excellent for audits because it pulls authoritative data directly from the National Vulnerability Database, ensuring your reports are based on official records.

**Can the NIST NVD MCP search for vulnerabilities by weakness type?**
Yes, you can search by CWE (Common Weakness Enumeration) to find all vulnerabilities related to specific issues like buffer overflows or cross-site scripting.

**Does the NIST NVD MCP require an API key?**
While it works without one, providing your NIST NVD API key will give your agent higher rate limits for more frequent searches.

**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.