Skip to main content
Glama
Alig1493

NVD MCP Server

search_cve_history

Retrieve change history for CVE records from the NVD, including event type, timestamp, and change details. Filter by date range, CVE ID, or event type to monitor vulnerability modifications.

Instructions

Search the NVD CVE Change History API for changes made to CVE records.

Returns a JSON string with pagination info and a list of change events, each containing the CVE ID, event type, source, timestamp, and change details.

Performance guidance — the history API is significantly slower than the CVE API:

  • Always set results_per_page to 2–5.

  • Narrow the date window to 7 days or less when using change_start_date / change_end_date. The maximum allowable range is 120 consecutive days.

  • Avoid querying by event_name alone without a date range — it scans the entire history database and will time out. Combine event_name with a date range.

  • For a specific CVE use cve_id; that is the fastest query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesNVD CVE History API 2.0 request model. The CVE Change History API is used to easily retrieve information on changes made to a single CVE or a collection of CVE from the NVD. This API provides additional transparency to the work of the NVD, allowing users to easily monitor when and why vulnerabilities change. The NVD has existed in some form since 1999 and the fidelity of this information has changed several times over the decades. Earlier records may not contain the level of detail available with more recent CVE records. This is most apparent on CVE records prior to 2015.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries the burden. It states returns JSON with pagination and change events, and notes performance characteristics (slower than CVE API). However, it does not detail output structure or mention potential timeouts beyond the given guidance.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Reasonably concise with three paragraphs: purpose, return info, then performance guidance. Information is front-loaded, though some details (like max range) appear both in description and schema. Could be slightly tighter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (nested input, output schema exists), the description covers purpose, return type, and performance. It lacks explanation of pagination mechanics or output field details, but the output schema compensates. Sufficient for an agent to use effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with detailed comments for each parameter. The tool description does not add extra semantic value beyond the schema; baseline 3 is appropriate as the schema already provides rich information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Search the NVD CVE Change History API for changes made to CVE records.' It specifies the resource (CVE change history) and action (search), though it does not explicitly distinguish from the sibling tool 'search_cves' beyond a performance hint.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit performance guidance: set results_per_page to 2-5, narrow date window to 7 days or less, avoid event_name without date range, and use cve_id for fastest queries. Also notes maximum 120-day range, giving clear when-to and how-to-use instructions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Alig1493/nvd-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server