cybersecurity-vuln-mcp

vuln_search

Search NIST NVD for CVEs using keyword, severity, date range, and KEV filter to identify relevant vulnerabilities.

Instructions

Search the NIST NVD for CVEs by keyword, severity, and date range.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vuln_search"
  }
}

Input Schema

Name	Required	Description
`keyword`	No	Search keyword (e.g., 'apache log4j')
`severity`	No	CVSS v3.1 severity
`pubStartDate`	No	Start date ISO format
`pubEndDate`	No	End date ISO format
`hasKev`	No	Only show actively exploited CVEs
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 6, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Without annotations, the description does not explicitly state the tool's read-only nature or any side effects. It merely describes the search functionality, leaving behavioral assumptions to the agent.

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?

The description is a single 12-word sentence that efficiently conveys the core purpose with no redundant information.

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

Completeness2/5

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

The description does not mention return format, pagination, or how results are ordered. With no output schema, this information is critical for an agent to understand how to use the output.

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?

The schema has 83% parameter description coverage, so the baseline is 3. The description only mentions three parameters (keyword, severity, date range) without adding new meaning beyond the schema.

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?

The description clearly states the tool searches the NIST NVD for CVEs by keyword, severity, and date range. It distinguishes itself from siblings like vuln_by_vendor (vendor-specific) and vuln_lookup_cve (single CVE lookup).

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus sibling tools like vuln_epss_top or vuln_kev_due_soon. The description lacks any context about alternatives or prerequisites.

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

Deploy Server