Skip to main content
Glama
Sign In
CVE Search MCP Server

CVE Search MCP Server

by Arnabdaz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_recent_cves

Get CVEs published in the last N days (1-365) with severity analysis and alert levels. Use this to identify recently disclosed vulnerabilities for security review.

Instructions

Get CVEs published in the last N days (1-365). Fast. Returns a list with severity analysis and alert level. Example: get_recent_cves(7, 30) — last week's top 30 CVEs.

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": "get_recent_cves"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
limitNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so description carries burden. It mentions 'Fast' (performance) and return content (severity analysis, alert level), but does not disclose potential pitfalls like rate limits, authentication needs, or whether results are real-time or cached.

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?

Extremely concise: purpose, behavior, and example in four lines. Information is front-loaded, with zero wasted words.

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?

Covers purpose, core behavior, and parameter usage. Given the simple tool (2 params, output schema exists) and lack of annotations, the description is nearly complete. Missing error handling or data freshness details, but overall sufficient.

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?

Input schema has 0% description coverage. The description uses an example to explain that 'days' sets the lookback period and 'limit' caps results, but does not explicitly detail each parameter's meaning, constraints, or default values 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 gets CVEs published in the last N days, with a specific scope (1-365 days). It distinguishes from siblings like search_cve_by_id or bulk_cve_lookup by emphasizing recency and providing an example.

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

Usage Guidelines3/5

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

The description implies usage via an example but does not explicitly state when to use this tool versus alternatives like 'search_by_keyword' or 'check_high_severity_cves'. There is no when-not guidance or mention of alternatives.

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