cve-cache
NPM · @WEISEER/CVE-CACHE-MCP
Recent CVE + GHSA cache for AI agents auditing dependencies (npm/PyPI/Cargo/Maven/Go).
Available components
Last scanned (3 hours ago)
Scores higher than 62% 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 Security98
- 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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 158 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 170 tokens (~42/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage80
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 40% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −2
- Stability: pass → 0.90 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 23 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 22 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.97 functional
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/@weiseer/cve-cache-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
find_for_package ~46
All CVEs affecting a package. Optionally filter by ecosystem.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | npm/pypi/cargo/maven/go |
| package_name | string | yes | – |
No output schema declared.
No examples provided.
list_recent_critical ~46
Recent CVEs with CVSS >= threshold. Default: 7-day high-severity feed.
| Name | Type | Req | Description |
|---|---|---|---|
| min_cvss | number | – | – |
| since_days | number | – | – |
No output schema declared.
No examples provided.
lookup_cve ~56
Full record for one CVE by ID. Cited NVD + GHSA URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| cve_id | string | yes | e.g. CVE-2024-12345 or GHSA-xxxx-xxxx-xxxx |
No output schema declared.
No examples provided.
severity_summary ~22
Counts by severity bucket across the snapshot. Quick agent triage view.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the cve-cache MCP server?
cve-cache runs locally as an npm package, launched with npx -y @weiseer/cve-cache-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 · @weiseer/cve-cache-mcp
claude mcp add weiseer-cve-cache -- npx -y @weiseer/cve-cache-mcp
What is the cve-cache MCP server?
cve-cache is an MCP server listed in the public MCP registry as io.github.weiseer/cve-cache. Recent CVE + GHSA cache for AI agents auditing dependencies (npm/PyPI/Cargo/Maven/Go). This page covers its npm package (@weiseer/cve-cache-mcp).
Is the cve-cache MCP server safe to use?
cve-cache scores 79 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. 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 cve-cache MCP server expose?
cve-cache exposes 4 tools: lookup_cve, find_for_package, list_recent_critical, severity_summary. Their descriptions and schemas cost roughly 170 tokens of context every time the server is loaded.
Is the cve-cache MCP server still maintained?
cve-cache 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 cve-cache MCP server under?
cve-cache declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.