CVErdict
NPM · CVERDICT-MCP
Read-only CVE triage: verdicts from CISA KEV, EPSS and exploit feeds, each reason linked.
Available components
Last scanned (3 hours ago)
Scores higher than 65% of npm servers
Category Security
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to markusweldon/cverdict). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 4 Nov 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/cverdict-mcp@0.1.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | markusweldon/cverdict |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/markusweldon/cverdict/.github/workflows/release-mcp.yml@refs/tags/mcp-v0.1.3 |
| Rekor log index | 3691502407 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:ae99e96d1f0d7d8eb0e1a77553708474d746a6204e7843a761c9a16ac97cbd11a51c75826330cb63ae90042cd320670c40128a6930b9253b2a08113be |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_verdict Verdicts for CVE IDs ~177
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.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | boolean | – | Also return the description, affected products, CWE, SSVC, exploit links, timeline and references. At most 5 IDs. |
| ids | array | yes | CVE IDs, e.g. ["CVE-2026-96951"]. |
| knob | integer | – | Evidence needed for Likely next, 30 to 80. Default 50, as on the site. |
No output schema declared.
No examples provided.
kev_due CISA KEV due dates ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
list_signal CVEs worth your time ~192
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
receipts Track record against CISA KEV ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | One CVE: its forward-log entry and its backtest entry. |
No output schema declared.
No examples provided.
search_cves Search the 30-day window ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Words that must all occur (case-insensitive), at most 8. |
| tiers | array | – | Only these tiers at the knob. |
No output schema declared.
No examples provided.
woke_up Old CVEs that woke up ~145
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
npm · cverdict-mcp
claude mcp add markusweldon-cverdict -- npx -y cverdict-mcp
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.