LeanGate
PYPI · LEANGATE
Checks agent-written Python against your repo: duplicate helpers, error handling, security.
Available components
Last scanned (14 hours ago)
Scores higher than 0% of PyPI servers
Category Developer Tools
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: LeanGate is in private beta; request access at https://leangates.com.
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security50
- No malware found by supply-chain analysis.Pass
- Known CVEs could not be checked: we could not find this package in its registry.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we could not find this package in its registry.Unverified
Provenance & Transparency0
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: the registry has no such package, so there's no artefact to verify. See how to fix → View diagnostics → Fail
- License check failed: the registry has no such package, so no license can be read. See how to fix → Fail
- Maintenance check failed: the registry has no such package, so there's no release history to read. See how to fix → Fail
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 867 tokens (~123/item across 7 items; 7 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 24 Oct 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 23 Oct 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 22 Oct 26 −12
- Malware scan: unverified → pass ▲ security
- 21 Oct 26 −13
- Malware scan: pass → unverified ▼ security
- 20 Oct 26 −12
- Malware scan: unverified → pass ▲ security
- 19 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 18 Oct 26 0
- Known CVEs: pass → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Provenance: pass → fail ▼ security
- Source repository: pass → fail ▼ security
- The code this package runs automatically changed: its declared build backend security
- The attested source repository moved: lambdabypi/leangate security
- Dependency health: 0.98 → unverified ▼ functional
- License: pass → fail ▼ functional
- Maintenance: pass → fail ▼ functional
- Licence: MIT functional
- Package version: 0.1.1 → 0.1.2 functional
- 17 Oct 26 62
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 24 Oct 2026 · Analysed pypi/leangate@0.1.2
Provenance Package not found
The registry answered that no such package exists, so no provenance could be looked up.
| Result | Package not found |
|---|---|
| Ecosystem | pypi |
| Reason | Metadata unavailable |
Background: How many MCP packages publish verified provenance →
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 →
check_dependency ~84
Call BEFORE adding a package. Checks it exists on PyPI (catches hallucinated names), known vulnerabilities (OSV.dev), maintenance, and whether something the project already has covers `purpose`. Returns recommendation: add | use_existing | avoid.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| purpose | string | – | – |
| repo | – | – | – |
| version | – | – | – |
No output schema declared.
No examples provided.
check_reuse ~131
Optional, before writing a general-purpose function or helper your own search didn't find. Describe what you are about to build in `intent` (e.g. "retry HTTP calls with exponential backoff"); optionally pass your draft in `code`. Returns the closest existing symbols, each with a decision: reuse | adapt | write_new; the repo's own helpers for library calls the intent touches (`house_helpers`); and project conventions. `write_new` means none of these few matches fits, not that the repo lacks it.
| Name | Type | Req | Description |
|---|---|---|---|
| code | – | – | – |
| intent | string | yes | – |
| repo | – | – | – |
No output schema declared.
No examples provided.
minimize ~98
Return a smaller version of a Python module with identical behavior. The rewrite (Nemotron) is pre-checked (Jev) and then run against `tests` in a sandbox. Tests must import from a module named `target`. Without tests, tests are generated. A rewrite that changes behavior is rejected and the original is returned.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
| findings | – | – | – |
| repo | – | – | – |
| tests | – | – | – |
No output schema declared.
No examples provided.
prove_equivalent ~80
Run the same tests (importing from module `target`) against two versions of a module. `equivalent` is null when there were no tests to run (none given, and none could be generated): unproven, not shown to differ.
| Name | Type | Req | Description |
|---|---|---|---|
| minimized | string | yes | – |
| original | string | yes | – |
| tests | – | – | – |
No output schema declared.
No examples provided.
record_feedback ~111
Tell LeanGate whether a finding was right. A rejected finding (accepted=false) is never raised again, except a security finding: only a person can waive one (`leangate waive`), so tell the user why you think it's wrong instead. If `note` states a project convention (e.g. "we always validate at API handlers"), it is remembered.
| Name | Type | Req | Description |
|---|---|---|---|
| accepted | boolean | yes | – |
| note | string | – | – |
| repo | – | – | – |
| signature | string | yes | – |
No output schema declared.
No examples provided.
show_report ~63
Open LeanGate's live dashboard (127.0.0.1 only) in the browser, showing the latest reports for this repo. Call it only when the user asks to see the report. It starts the local dashboard if it isn't running.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | – | – | – |
No output schema declared.
No examples provided.
verify_lean ~167
Call when you finish a change, before you report done or commit. Checks new code for three things. Bloat: duplicates of existing code, dead code, unused imports, redundant checks, single-implementation abstractions, pass-through wrappers, hand-rolled stdlib functions, unneeded dependencies. Error handling: swallowed exceptions, missing timeouts, unchecked subprocesses, unclosed files, imports of project modules or names that don't exist. Security: injection, hard-coded secrets, verify=False, unsafe deserialization, unknown or vulnerable packages. `diff` is a unified diff; omit it to check the working tree against HEAD. Returns gate=pass|block with findings. Fix blocking findings or reject wrong ones via record_feedback.
| Name | Type | Req | Description |
|---|---|---|---|
| diff | – | – | – |
| repo | – | – | – |
No output schema declared.
No examples provided.
How do I install the LeanGate MCP server?
LeanGate runs locally as a PyPI package, launched with uvx leangate. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · leangate
claude mcp add lambdabypi-leangate -- uvx leangate
What is the LeanGate MCP server?
LeanGate is an MCP server listed in the public MCP registry as io.github.lambdabypi/leangate. Checks agent-written Python against your repo: duplicate helpers, error handling, security. This page covers its PyPI package (leangate).
Is the LeanGate MCP server safe to use?
LeanGate scores 0 out of 100 on VerifyMCP. 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 LeanGate MCP server expose?
LeanGate exposes 7 tools: check_reuse, verify_lean, minimize, prove_equivalent, check_dependency, and 2 more. Their descriptions and schemas cost roughly 734 tokens of context every time the server is loaded.
Is the LeanGate MCP server still maintained?
LeanGate is marked deprecated in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.