Skip to main content
Glama

cisa-cybersecurity-mcp-server

cisa_check_cve_status

cisa_check_cve_status
Read-onlyIdempotent

Check CVE IDs against the CISA Known Exploited Vulnerabilities catalog — up to 200 per call, served from a cached catalog snapshot at no upstream cost. Returns, per CVE, whether it is in KEV and if so the date added, the federal remediation due date, days remaining or days overdue, which binding operational directive the entry cites, the required action text, whether it is linked to ransomware campaigns, whether it falls in the three-day forensic-triage tier, CISA's own vendor and product labels, associated CWEs, and the reference URLs parsed from the entry's notes. A CVE that is not in KEV is a normal result, not an error. For a large batch, detail "summary" keeps only the triage fields — the deadline and overdue status, directive, ransomware and forensic-triage flags, and vendor and product labels — and drops the descriptive text, CWEs, and references, so a full batch stays compact. The CWE IDs returned chain directly into the cwe filter of cisa_search_kev and cisa_search_ics_advisories, and the parsed NVD reference gives the canonical record for scoring detail. For the reverse direction — which ICS advisories cover a CVE — pass it as cve to cisa_search_ics_advisories, or set inKev there to list the advisories covering any KEV CVE.

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": {
      "cveIds": "<cveIds>"
    },
    "name": "cisa_check_cve_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
cveIdsYesCVE identifiers to check, up to 1,000 accepted and 200 processed per call. Oversized batches return normalized unprocessedIds for a follow-up call unless normalization is disabled. The whole batch costs zero upstream requests — pair a large batch with detail "summary".
detailNofull returns every field of each in-KEV entry. summary returns only cveId, inKev, dateAdded, dueDate, daysUntilDue, overdue, directive, vendorProject, product, knownRansomwareCampaignUse, and forensicTriage — the triage view for a large batch. Not-in-KEV results are the same under both.full

Output Schema

NameRequiredDescriptionDefault
asOfNoThe UTC date daysUntilDue and overdue were computed against, YYYY-MM-DD.
errorNoPresent when the call failed. Absent on success.
noticeNoGuidance for oversized batches or when none of the processed CVEs are in the catalog.
catalogNoWhich catalog snapshot answered this call.
resultsNoOne result per processed CVE, in the order supplied.
foundCountNoHow many of the processed CVEs are in the catalog.
summaryNoteNoPresent only under detail "summary": which fields each in-KEV result omits and how to restore them.
notFoundCountNoHow many of the processed CVEs are not in the catalog.
unprocessedIdsNoNormalized CVE IDs not processed; send these in a follow-up call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedOutput schema / properties / foundCount / description
      Previous value: -"How many of the requested CVEs are in the catalog."New value: +"How many of the processed CVEs are in the catalog."
    • changedOutput schema / properties / notFoundCount / description
      Previous value: -"How many of the requested CVEs are not in the catalog."New value: +"How many of the processed CVEs are not in the catalog."
    • changedOutput schema / properties / notice / description
      Previous value: -"Guidance when none of the supplied CVE IDs are in the catalog."New value: +"Guidance for oversized batches or when none of the processed CVEs are in the catalog."
    • changedOutput schema / properties / results / items / description
      Previous value: -"One KEV catalog entry, or a not-in-KEV result carrying only cveId and inKev. Under cisa_check_cve_status detail \"summary\" an entry carries only cveId, inKev, the dates and deadline status, directive, vendor and product labels, and the ransomware and forensic-triage flags."New value: +"One KEV catalog entry, or a not-in-KEV result carrying only cveId and inKev. Under detail \"summary\" in cisa_check_cve_status or cisa_search_kev, an entry carries only cveId, inKev, the dates and deadline status, directive, vendor and product labels, and the ransomware and forensic-triage flags."
  2. Changed6 schema fields changed
    • changedInput schema / properties / cveIds / description
      Previous value: -"CVE identifiers to check, up to 200 per call. The whole batch costs zero upstream requests, so a full CVE alias list from a dependency audit can be checked in one call — pair a large batch with detail \"summary\"."New value: +"CVE identifiers to check, up to 1,000 accepted and 200 processed per call. Oversized batches return normalized unprocessedIds for a follow-up call unless normalization is disabled. The whole batch costs zero upstream requests — pair a large batch with detail \"summary\"."
    • changedInput schema / properties / cveIds / maxItems
      Previous value: -200New value: +1000
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `catalog_unavailable`: No KEV catalog snapshot is held and the fetch from cisa.gov failed. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `read_limit_exceeded`: The batch exceeds the per-call cap and input normalization is disabled. `catalog_unavailable`: No KEV catalog snapshot is held and the fetch from cisa.gov failed. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "catalog_unavailable"
      -]New value: +[
      +  "read_limit_exceeded",
      +  "catalog_unavailable"
      +]
    • changedOutput schema / properties / results / description
      Previous value: -"One result per requested CVE, in the order supplied."New value: +"One result per processed CVE, in the order supplied."
    • addedOutput schema / properties / unprocessedIds
      Added value: +{
      +  "description": "Normalized CVE IDs not processed; send these in a follow-up call.",
      +  "items": {
      +    "pattern": "^CVE-[0-9]{4}-[0-9]{4,19}$",
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  3. Changed12 schema fields changed
    • changedInput schema / properties / cveIds / description
      Previous value: -"CVE identifiers to check, up to 200 per call. The whole batch costs zero upstream requests, so a full CVE alias list from a dependency audit can be checked in one call."New value: +"CVE identifiers to check, up to 200 per call. The whole batch costs zero upstream requests, so a full CVE alias list from a dependency audit can be checked in one call — pair a large batch with detail \"summary\"."
    • addedInput schema / properties / detail
      Added value: +{
      +  "default": "full",
      +  "description": "full returns every field of each in-KEV entry. summary returns only cveId, inKev, dateAdded, dueDate, daysUntilDue, overdue, directive, vendorProject, product, knownRansomwareCampaignUse, and forensicTriage — the triage view for a large batch. Not-in-KEV results are the same under both.",
      +  "enum": [
      +    "full",
      +    "summary"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / properties / results / items / description
      Previous value: -"One KEV catalog entry, or a not-in-KEV result carrying only cveId and inKev."New value: +"One KEV catalog entry, or a not-in-KEV result carrying only cveId and inKev. Under cisa_check_cve_status detail \"summary\" an entry carries only cveId, inKev, the dates and deadline status, directive, vendor and product labels, and the ransomware and forensic-triage flags."
    • changedOutput schema / properties / results / items / properties / cwes / description
      Previous value: -"Associated CWEs. Empty on 175 entries, so a CWE filter excludes those."New value: +"Associated CWEs. Empty on some entries, and a CWE filter excludes those. Absent under detail \"summary\"."
    • changedOutput schema / properties / results / items / properties / directive / description
      Previous value: -"The binding operational directive the entry cites, or null when it cites neither — 1,277 of 1,716 entries name none, and none is never inferred from age."New value: +"The binding operational directive the entry cites, or null when it cites neither — most entries name none, and none is never inferred from age."
    • changedOutput schema / properties / results / items / properties / kevUrl / description
      Previous value: -"Absolute URL of the KEV catalog page for this CVE."New value: +"Absolute URL of the KEV catalog page for this CVE. Absent under detail \"summary\"."
    • changedOutput schema / properties / results / items / properties / notesCommentary / description
      Previous value: -"Free prose from the notes field, present when the entry opens with prose."New value: +"The prose segments of the notes field, verbatim with any URLs they contain; present when the notes carry prose. Absent under detail \"summary\"."
    • changedOutput schema / properties / results / items / properties / references / description
      Previous value: -"Reference URLs parsed from the notes field, each classified by kind."New value: +"Every reference URL in the notes field, in notes order, each classified by kind. Absent under detail \"summary\"."
    • changedOutput schema / properties / results / items / properties / requiredAction / description
      Previous value: -"CISA's required-action text for the entry, verbatim."New value: +"CISA's required-action text for the entry, verbatim. Absent under detail \"summary\"."
    • changedOutput schema / properties / results / items / properties / shortDescription / description
      Previous value: -"CISA's one-paragraph description."New value: +"CISA's one-paragraph description. Absent under detail \"summary\"."
    • changedOutput schema / properties / results / items / properties / vulnerabilityName / description
      Previous value: -"CISA's short name for the vulnerability."New value: +"CISA's short name for the vulnerability. Absent under detail \"summary\"."
    • addedOutput schema / properties / summaryNote
      Added value: +{
      +  "description": "Present only under detail \"summary\": which fields each in-KEV result omits and how to restore them.",
      +  "type": "string"
      +}
  4. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and idempotentHint, so the description carries the rest and does well: it discloses the cached snapshot with zero upstream cost, the 200-per-call processing limit, and that non-KEV results are normal rather than errors. It slightly under-sells the oversized-batch behavior (1,000 accepted, remainder returned as unprocessedIds), which only the schema spells out, so the two texts sit in mild tension rather than full alignment.

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?

Purpose and cost profile are front-loaded, and the routing sentences at the end are useful rather than filler. The long enumeration of per-CVE return fields largely duplicates the existing output schema and could be trimmed, making it denser than necessary.

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 two-parameter, read-only batch lookup with an output schema already present, the description covers scope, cost, batching limits, tier trade-offs, error semantics, and sibling routing. An agent has everything needed to call it correctly on the first attempt.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description still adds value by explaining why the detail tiers matter operationally ("so a full batch stays compact") and by enumerating which triage fields survive summary mode. It stops short of restating the CVE ID normalization behavior, but the schema covers that.

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 ("Check CVE IDs against the CISA Known Exploited Vulnerabilities catalog") and immediately scopes it with batching and caching details. It is clearly distinguishable from siblings like cisa_search_kev, which searches the catalog rather than checking specific IDs.

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 explicit conditional guidance: use detail "summary" for large batches, treat not-in-KEV as a normal result, and route the reverse question ("which ICS advisories cover a CVE") to cisa_search_ics_advisories with either the cve or inKev parameter. It also names the forward chaining path into cisa_search_kev and cisa_search_ics_advisories via the returned CWE IDs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.