CVE Risk Check

Rank several CVEs

check_cves

Read-onlyIdempotent

Rank several CVEs. Use this when the user has a list of CVE ids and wants to know which to deal with first, such as "which of these CVEs should I patch first?". Pass up to 10 CVE ids. Returns each one's priority, CVSS score, CISA exploited-list status and EPSS score, most urgent first, with a count per priority. An id NVD could not be asked about in this call is marked deferred; ask for it again later. It does not know which software the user runs.

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": {
      "cves": "<cves>"
    },
    "name": "check_cves"
  }
}

Input Schema

Name	Required	Description	Default
`cves`	Yes	Up to 10 CVE ids

Output Schema

Name	Required	Description
`count`	Yes
`counts`	Yes
`notice`	Yes
`source`	Yes
`results`	Yes
`deferred`	No	Ids not read in this call to stay within NVD's request limit; ask for them again in a minute

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026

addedOutput schema / properties / deferred

Added value: +{
+  "description": "Ids not read in this call to stay within NVD's request limit; ask for them again in a minute",
+  "type": "integer"
+}

addedOutput schema / properties / results / items / properties / osv

Added value: +{
+  "description": "The OSV.dev advisory, present for an advisory id or a CVE that NVD has not published yet",
+  "properties": {
+    "aliases": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "id": {
+      "type": "string"
+    },
+    "packages": {
+      "description": "Each affected package and the releases that fix it, one per release line",
+      "items": {
+        "properties": {
+          "ecosystem": {
+            "type": "string"
+          },
+          "fixed_in": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "severity": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "summary": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedOct 30, 2026

addedOutput schema / properties / results / items / properties / affected

Added value: +{
+  "description": "Vulnerable product lines from NVD's CPE data: affected from `from`, fixed in `fixed_in` (or last affected `up_to`)",
+  "items": {
+    "properties": {
+      "fixed_in": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "from": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "product": {
+        "type": "string"
+      },
+      "up_to": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / results / items / properties / cna_cvss

Added value: +{
+  "description": "The vendor (CNA) score when it differs from NVD's",
+  "properties": {
+    "score": {
+      "type": "number"
+    },
+    "scored_by": {
+      "enum": [
+        "NVD",
+        "CNA"
+      ],
+      "type": "string"
+    },
+    "severity": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "version": {
+      "type": "string"
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}

Changed1 schema field changedOct 5, 2026

removedOutput schema / properties / note_from_openkrill

Removed value: -{
-  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
-  "type": "string"
-}

Changed1 schema field changedOct 4, 2026

addedOutput schema / properties / note_from_openkrill

Added value: +{
+  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
+  "type": "string"
+}

First observedOct 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Adds real context beyond annotations: returns priority, CVSS, CISA exploited-list status and EPSS, sorted most-urgent-first, with per-priority counts. The 'deferred' semantics for ids NVD couldn't be queried is a genuinely useful operational disclosure. Annotations already cover read-only/idempotent safety, so the remaining context is what the description needed to add.

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 is front-loaded in the first sentence, followed by usage, then output shape and caveats. Dense but purposeful. Slightly long; the 'deferred' sentence could be tightened, but every sentence carries information.

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?

With one parameter and a full output schema, the description supplies everything else an agent needs: when to use it, what comes back, ordering, and the deferred edge case. The explicit 'does not know which software the user runs' limits prevent over-trusting the ranking.

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 id format, max 10, uniqueness and required-ness are already documented. The description repeats 'up to 10 CVE ids' without adding format or syntax detail. Baseline 3 is appropriate when the schema does the work.

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 ('Rank') and resource ('CVEs'), and distinguishes itself from the singular sibling check_cve by making clear this handles a list. The example question clarifies the ranking output an agent should expect.

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?

Explicitly says when to use it (user has a list of CVE ids and wants to know which to patch first) and implies the sibling distinction by contrast with single-id lookup. The scope exclusion ('It does not know which software the user runs') tells the agent what this cannot answer.

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

All CVE Risk Check tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.