Preventionlabs
NPM · PREVENTIONLABS-MCP
See what's broken on a live website from the outside: errors, uptime, DNS, HTTPS, leaked files.
Available components
Last scanned (3 hours ago)
Scores higher than 37% of npm servers
Category Monitoring and Observability
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
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (UNLICENSED) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 0 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 942 tokens (~314/item across 3 items; 3 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 Management10
- Stability observed for 3 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 3 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.
- 18 Oct 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- 17 Oct 26 −11
- Known CVEs: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Dependency health: 0.85 → unverified ▼ functional
- Schema quality: pass → fail ▼ functional
- Schema quality: unverified → 100 ▲ functional
- Stability: unverified → 0.07 ▲ functional
- Package version: 1.0.1 → 1.2.0 functional
- Package version: 1.0.1 → 1.1.0 functional
- 15 Oct 26 +33
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 14 Oct 26 31
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 18 Oct 2026 · Analysed npm/preventionlabs-mcp@1.2.0
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 | 31 |
| 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 →
latest_report Read the latest report ~97
Returns the most recent Preventionlabs report for a verified website, how long ago it ran, and how many runs are left. Costs no run. Use it to reread a result, or to check what's left before deciding whether to run a new report. It shows the site as it was then, not now.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | – | The website, e.g. example.com. Leave empty when the account has only one verified site. |
No output schema declared.
No examples provided.
list_sites List Preventionlabs sites ~30
Lists the websites in the Preventionlabs account, and whether each is verified. Only verified sites can be checked.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_report Check a live website ~179
Runs a new Preventionlabs report on one of the account's verified websites and returns it as Markdown: what's broken on the live site and where (pages, browser errors, uptime, DNS, HTTPS, redirects, leaked files, email setup, and Cloudflare errors, deploys and recent changes when Cloudflare is connected), with evidence and what to do. Read-only. Takes 15 seconds to about a minute. Use it after a deploy or a DNS, hosting or email change, when the site seems down or broken, and again after a fix to prove it worked. Each run uses one of the site's daily runs (usually 2 per 24 hours); to reread the last result, use latest_report instead.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | – | The website, e.g. example.com. Leave empty when the account has only one verified site. |
No output schema declared.
No examples provided.
How do I install the Preventionlabs MCP server?
Preventionlabs runs locally as an npm package, launched with npx -y preventionlabs-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 · preventionlabs-mcp
claude mcp add au-com-preventionlabs-preventionlabs -- npx -y preventionlabs-mcp
What is the Preventionlabs MCP server?
Preventionlabs is an MCP server listed in the public MCP registry as au.com.preventionlabs/preventionlabs. See what's broken on a live website from the outside: errors, uptime, DNS, HTTPS, leaked files. This page covers its npm package (preventionlabs-mcp).
Is the Preventionlabs MCP server safe to use?
Preventionlabs scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 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 Preventionlabs MCP server expose?
Preventionlabs exposes 3 tools: list_sites, run_report, latest_report. Their descriptions and schemas cost roughly 306 tokens of context every time the server is loaded.
Is the Preventionlabs MCP server still maintained?
Preventionlabs is still listed as active in the MCP registry. We last reached this channel on 18 October 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 Preventionlabs MCP server under?
Preventionlabs declares the UNLICENSED licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.