Skip to main content
Glama
K4PXD

cve-mcp-server

by K4PXD
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get CVE details

cve_get_details
Read-onlyIdempotent

Retrieve complete NVD details for a CVE, including CVSS scores, CWE, CPEs, references, plus CISA KEV and EPSS exploitation signals.

Instructions

Retrieve complete, authoritative details for a single CVE from the NIST NVD, enriched with real-time exploitation signals.

Combines: NVD description, CVSS v2/v3.1/v4 base scores + vectors, CWE weakness types, affected-product CPE strings, and reference URLs — plus (by default) CISA KEV actively-exploited status and the EPSS exploitation-probability score.

Args:

  • cve_id (string): CVE identifier, e.g. "CVE-2021-44228".

  • include_kev (boolean): Add CISA KEV status (default: true).

  • include_epss (boolean): Add EPSS score (default: true).

  • response_format ('markdown' | 'json'): Output format (default: 'markdown').

Returns (json): { id, published, lastModified, vulnStatus, descriptions, cvss[], cwes[], references[], cpe[], kev, epss }.

Examples:

  • "Tell me everything about Log4Shell" -> cve_id="CVE-2021-44228".

  • "Is CVE-2023-23397 being exploited?" -> include_kev=true, include_epss=true.

Errors:

  • "Invalid CVE ID ..." if the ID is malformed.

  • "No NVD record found for " if the CVE does not exist in NVD.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cve_idYesCVE identifier, e.g. 'CVE-2021-44228'.
include_kevNoEnrich with CISA KEV (actively-exploited) status.
include_epssNoEnrich with the EPSS exploitation-probability score.
response_formatNoOutput format: 'markdown' (default, human-readable) or 'json' (full structured data).markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag read-only/idempotent behavior, and the description adds real behavioral detail: NVD as source, optional KEV/EPSS enrichment defaulting to true, two output formats, the full JSON return shape, and expected error strings. It doesn't mention rate limits or auth, but those are not essential given the annotations.

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?

The description is structured into purpose, args, returns, examples, and errors, with the purpose front-loaded. It is slightly redundant with the input schema in the Args block, but the return shape and error strings are valuable and not otherwise present.

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

Completeness5/5

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

For a single-record lookup with four parameters and no output schema, this is complete: it defines the required identifier, optional enrichment flags, output format, default behavior, return fields, and failure modes. An agent can call it correctly without additional context.

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 coverage is 100%, so the schema already fully documents all four parameters and defaults. The description restates these in Args and adds illustrative query mappings, but no new parameter-level semantics or constraints beyond what the schema provides.

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?

Opens with 'Retrieve complete, authoritative details for a single CVE from the NIST NVD' – a specific verb, resource, and single-record scope. The combination list (NVD description, CVSS, CWE, CPE, references, KEV, EPSS) clearly differentiates it from focused sibling tools like cve_get_kev or cve_get_pocs.

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

Usage Guidelines4/5

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

The single-CVE scope and examples ('Tell me everything about Log4Shell' -> cve_id; 'Is CVE-2023-23397 being exploited?' -> include flags) make intended use concrete. It does not explicitly name alternatives or state when not to use it, so it stops short of a full 5.

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

Deploy Server

Other Tools