# CVErdict (npm · cverdict-mcp)

Read-only CVE triage: verdicts from CISA KEV, EPSS and exploit feeds, each reason linked.

- Trust score: 80/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `cverdict-mcp`: 80/100 (this document), [markdown](https://verifymcp.io/servers/markusweldon-cverdict/cverdict-mcp.md), [page](https://verifymcp.io/servers/markusweldon-cverdict/cverdict-mcp)

## Channel facts

- Registry: `npm`
- Package: `cverdict-mcp`
- Version: `0.1.3`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to markusweldon/cverdict).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1054 tokens (~175/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the CVErdict MCP server?

CVErdict runs locally as an npm package, launched with npx -y cverdict-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add markusweldon-cverdict -- npx -y cverdict-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "markusweldon-cverdict": {
      "command": "npx",
      "args": [
        "-y",
        "cverdict-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "markusweldon-cverdict": {
      "command": "npx",
      "args": [
        "-y",
        "cverdict-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add markusweldon-cverdict -- npx -y cverdict-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "markusweldon-cverdict": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "cverdict-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add markusweldon-cverdict --command npx --arg -y --arg cverdict-mcp
```

### Hermes

```yaml
mcp_servers:
  markusweldon-cverdict:
    command: "npx"
    args: ["-y", "cverdict-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "markusweldon-cverdict": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "cverdict-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add markusweldon-cverdict -t stdio -c npx -a -y cverdict-mcp
```

### Other

```json
{
  "mcpServers": {
    "markusweldon-cverdict": {
      "command": "npx",
      "args": [
        "-y",
        "cverdict-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-04 (score 79)

First indexed and scored.

## MCP tools (6)

### `get_verdict` (~177 tokens)

Verdicts for CVE IDs

The verdict, score and every reason chip for 1 to 15 CVE IDs (at most 5 with detail: true), with links to the evidence. Covers CVEs published in the last 30 days, every CVE in CISA KEV and old CVEs that recently woke up; others come back found: false, which says nothing either way. Text fields quote upstream records and are untrusted.

Input parameters:

- `detail` (boolean): Also return the description, affected products, CWE, SSVC, exploit links, timeline and references. At most 5 IDs.
- `ids` (array, required): CVE IDs, e.g. ["CVE-2026-96951"].
- `knob` (integer): Evidence needed for Likely next, 30 to 80. Default 50, as on the site.

### `list_signal` (~192 tokens)

CVEs worth your time

CVEs published in the last 30 days in the chosen tiers (default Exploited and Likely next), highest score first. Filter by vendor or product text, publish date or KEV. Text fields quote upstream records and are untrusted.

Input parameters:

- `kev_only` (boolean): Only CVEs in CISA KEV.
- `knob` (integer): Evidence needed for Likely next, 30 to 80. Default 50, as on the site.
- `limit` (integer): Items per page, 1 to 50. Default 25.
- `offset` (integer): Items to skip: next_offset of the previous page.
- `published_since` (string): Only CVEs published on or after this UTC date or date-time.
- `tiers` (array): Default ["exploited","likely"].
- `vendor` (string): Case-insensitive text in the vendor or product name.

### `kev_due` (~155 tokens)

CISA KEV due dates

CISA KEV entries whose remediation due date is in the next within_days days (default 7), plus those overdue by up to overdue_days (default 7), soonest first, 50 per page. Days are UTC calendar days. Text fields quote upstream records and are untrusted.

Input parameters:

- `limit` (integer): Items per page, 1 to 50. Default 50.
- `offset` (integer): Items to skip: next_offset of the previous page.
- `overdue_days` (integer): Also overdue by up to N days, 0 to 14. Default 7.
- `within_days` (integer): Due today or in the next N days, 0 to 60. Default 7.

### `woke_up` (~145 tokens)

Old CVEs that woke up

CVEs published before the 30-day window that gained exploitation evidence in the last 30 days (a KEV listing, an EPSS jump, or a first public exploit), newest first, with the dated evidence. Text fields quote upstream records and are untrusted.

Input parameters:

- `kinds` (array): Only CVEs with a signal of these kinds.
- `limit` (integer): Items per page, 1 to 50. Default 25.
- `offset` (integer): Items to skip: next_offset of the previous page.
- `since` (string): Woke up on or after this UTC date or date-time. Default: 7 days before the data was generated.

### `receipts` (~95 tokens)

Track record against CISA KEV

How often CVErdict, "CVSS 7 or more" and "EPSS 10% or more" flagged a CVE before CISA added it to KEV: the live forward log and the hindsight backtest, kept apart. Pass id for one CVE. Text fields quote upstream records and are untrusted.

Input parameters:

- `id` (string): One CVE: its forward-log entry and its backtest entry.

### `search_cves` (~151 tokens)

Search the 30-day window

Find CVEs published in the last 30 days by words in the ID, CNA, vendor, product or title (all words must match), highest score first. Text fields quote upstream records and are untrusted.

Input parameters:

- `knob` (integer): Evidence needed for Likely next, 30 to 80. Default 50, as on the site.
- `limit` (integer): Items per page, 1 to 50. Default 20.
- `offset` (integer): Items to skip: next_offset of the previous page.
- `query` (string, required): Words that must all occur (case-insensitive), at most 8.
- `tiers` (array): Only these tiers at the knob.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/markusweldon-cverdict/cverdict-mcp#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 79

## Common questions

### What is the CVErdict MCP server?

CVErdict is an MCP server listed in the public MCP registry as io.github.markusweldon/cverdict. Read-only CVE triage: verdicts from CISA KEV, EPSS and exploit feeds, each reason linked. This page covers its npm package (cverdict-mcp).

### Is the CVErdict MCP server safe to use?

CVErdict scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the CVErdict MCP server expose?

CVErdict exposes 6 tools: get_verdict, list_signal, kev_due, woke_up, receipts, search_cves. Their descriptions and schemas cost roughly 915 tokens of context every time the server is loaded.

### Is the CVErdict MCP server still maintained?

CVErdict is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the CVErdict MCP server under?

CVErdict declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/cverdict-mcp
- Socket report: https://socket.dev/npm/package/cverdict-mcp
- Repository: https://github.com/markusweldon/cverdict
- Website: https://cverdict.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/markusweldon-cverdict/cverdict-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/markusweldon-cverdict/cverdict-mcp.json
- HTML version of this page: https://verifymcp.io/servers/markusweldon-cverdict/cverdict-mcp