LeakRank Guard
NPM · LEAKRANK-GUARD
Scans code changes for leaked secrets and insecure config, with actionable fixes for AI agents.
Available components
Last scanned (5 hours ago)
Scores higher than 50% 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
- 0 of 13 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency19
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 98 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 94 tokens (~31/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
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 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 31 Oct 26 +1
- Stability: 0.97 → pass security
- 30 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 +1
- Stability: 0.97 → pass security
- 23 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +1
- Stability: 0.97 → pass security
- 15 Oct 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.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 −1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 80.
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/leakrank-guard@0.2.3
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 13 packages
| Packages resolved | 13 |
|---|---|
| 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 →
guard_scan_baseline ~31
Full-repo baseline scan. Run once at install or on explicit user request. Costs 10 credits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
guard_scan_diff ~47
Scan the current git working-tree changes (or provided files) for leaked secrets and config risks. Run after completing a code change. Costs 1 credit.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | – | – |
No output schema declared.
No examples provided.
guard_status ~16
Report subscription status and remaining scan credits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the LeakRank Guard MCP server?
LeakRank Guard runs locally as an npm package, launched with npx -y leakrank-guard. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · leakrank-guard
claude mcp add prototeemo-leakrank-guard -- npx -y leakrank-guard
What is the LeakRank Guard MCP server?
LeakRank Guard is an MCP server listed in the public MCP registry as io.github.ProtoTeemo/leakrank-guard. Scans code changes for leaked secrets and insecure config, with actionable fixes for AI agents. This page covers its npm package (leakrank-guard).
Is the LeakRank Guard MCP server safe to use?
LeakRank Guard scores 75 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 LeakRank Guard MCP server expose?
LeakRank Guard exposes 3 tools: guard_scan_diff, guard_scan_baseline, guard_status. Their descriptions and schemas cost roughly 94 tokens of context every time the server is loaded.
Is the LeakRank Guard MCP server still maintained?
LeakRank Guard 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 LeakRank Guard MCP server under?
LeakRank Guard declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.