io.github.doazvjettu/leakguard-mcp
PYPI · LEAKGUARD-MCP
Static analyzer flagging lookahead bias & data leakage in ML/trading code before backtest.
Available components
Last scanned (12 hours ago)
Scores higher than 75% of PyPI servers
Category Testing and QA
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
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 18 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 (MIT).Pass
- Actively maintained (last published 144 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 166 tokens (~33/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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 −3
- Stability: pass → 0.77 functional
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.97 functional
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 0
- Stability: pass → 0.97 functional
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 pypi/leakguard-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 | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 18 packages
| Packages resolved | 18 |
|---|---|
| Stale | 1 |
| 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 →
explain_rule Explain Rule ~35
Long-form rationale and canonical fix pattern for one rule id (e.g. 'LG001').
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
lint_code Lint Code ~37
Scan a source string for leakage patterns. Returns {ok, parse_error, findings}.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
| filename | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
lint_file Lint File ~36
Scan a single file on disk. Returns {ok, parse_error, findings} or an error dict.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
lint_paths Lint Paths ~35
Scan every file matching a glob. Returns {path: {ok, parse_error, findings}}.
| Name | Type | Req | Description |
|---|---|---|---|
| pattern | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_rules List Rules ~23
Full rule catalog with id, name, severity, and one-line summary.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
How do I install the io.github.doazvjettu/leakguard-mcp server?
io.github.doazvjettu/leakguard-mcp runs locally as a PyPI package, launched with uvx leakguard-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · leakguard-mcp
claude mcp add doazvjettu-leakguard-mcp -- uvx leakguard-mcp
What is the io.github.doazvjettu/leakguard-mcp server?
io.github.doazvjettu/leakguard-mcp is listed in the public MCP registry as io.github.doazvjettu/leakguard-mcp. Static analyzer flagging lookahead bias & data leakage in ML/trading code before backtest. This page covers its PyPI package (leakguard-mcp).
Is the io.github.doazvjettu/leakguard-mcp server safe to use?
io.github.doazvjettu/leakguard-mcp scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 io.github.doazvjettu/leakguard-mcp server expose?
io.github.doazvjettu/leakguard-mcp exposes 5 tools: lint_code, lint_file, lint_paths, list_rules, explain_rule. Their descriptions and schemas cost roughly 166 tokens of context every time the server is loaded.
Is the io.github.doazvjettu/leakguard-mcp server still maintained?
io.github.doazvjettu/leakguard-mcp 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 io.github.doazvjettu/leakguard-mcp server under?
io.github.doazvjettu/leakguard-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.