vulnerability-exposure-mcp

Overview Schema Source Related Servers Discussions Admin

NVD CVE lookup

nvd_lookup

Read-onlyIdempotent

Fetches the full NVD record for a CVE, including CVSS, CWE, affected product ranges, CISA KEV, EPSS, and references. Use it for CVEs without an existing version-check record or to review full details.

Instructions

Full NVD record for one CVE (e.g. 'CVE-2021-44228'): description, CVSS, CWE, affected product ranges, CISA KEV and EPSS. Not needed for CVEs a version check already returned (they carry severity, EPSS, KEV, exploit and fix): use it for a CVE you have no record of, or to read one's full description and references.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cve_id": "<cve_id>"
    },
    "name": "nvd_lookup"
  }
}

Input Schema

Name	Required	Description	Default
`cve_id`	Yes	One CVE ID, e.g. 'CVE-2021-44228'.
`investigation_id`	No	The investigation_id from investigate_target. Pass it so the result counts toward that investigation's evidence, budget and key facts; without it the lookup runs on its own.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.1Oct 29, 2026

addedInput schema / properties / cve_id / description

Added value: +"One CVE ID, e.g. 'CVE-2021-44228'."

addedInput schema / properties / investigation_id / description

Added value: +"The investigation_id from investigate_target. Pass it so the result counts toward that investigation's evidence, budget and key facts; without it the lookup runs on its own."

First observedv0.1.0Oct 25, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds the return payload contents, which matters because there is no output schema, and warns that the lookup is redundant when a version check already supplied the data. It does not mention upstream rate limits or failure behavior on an unknown CVE ID, which keeps it off a 5.

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

Conciseness5/5

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

Two sentences, front-loaded with what is returned, then the exclusion and the positive cases. The parenthetical field lists are dense but each item earns its place by defining the payload.

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?

With no output schema, the description compensates by enumerating the record's fields, and the investigation_id side effects are documented in the schema. What is missing is edge-case behavior (invalid or withdrawn CVE IDs, upstream throttling) for a single-parameter external lookup.

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%, including the investigation_id note about evidence, budget and key facts, so the schema carries the parameter semantics. The description only repeats the CVE ID format example that the schema already provides. Baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ('Full NVD record for one CVE') and immediately enumerates what that record contains (description, CVSS, CWE, affected ranges, KEV, EPSS). This clearly separates it from cve_search (search) and version_specific_vulnerability_check (already-returned enriched data).

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?

Gives an explicit when-NOT: not needed for CVEs a version check already returned, with the reason (they already carry severity, EPSS, KEV, exploit, fix). It then names the two positive cases: a CVE you have no record of, or reading full description and references. An agent can route correctly without opening the schema.

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