# LeanGate (pypi · leangate)

Checks agent-written Python against your repo: duplicate helpers, error handling, security.

- Trust score: 0/100 (low)
- Change this week: −62
- Registry status: deprecated
- Liveness: dead
- Owner verified: no
- Last scored: 2026-10-24

> **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.

## Components

- pypi · `leangate`: 0/100 (this document), [markdown](https://verifymcp.io/servers/lambdabypi-leangate/leangate.md), [page](https://verifymcp.io/servers/lambdabypi-leangate/leangate)

## Channel facts

- Registry: `pypi`
- Package: `leangate`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-24.

- **Supply Chain Security**: 50/100
  - No malware found by supply-chain analysis.
  - Known CVEs could not be checked: we could not find this package in its registry.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we could not find this package in its registry.
- **Provenance & Transparency**: 0/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: the registry has no such package, so there's no artefact to verify.
  - License check failed: the registry has no such package, so no license can be read.
  - Maintenance check failed: the registry has no such package, so there's no release history to read.
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**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.

## Install

### 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.

### Claude

```bash
claude mcp add lambdabypi-leangate -- uvx leangate
```

### Cursor

```json
{
  "mcpServers": {
    "lambdabypi-leangate": {
      "command": "uvx",
      "args": [
        "leangate"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lambdabypi-leangate": {
      "command": "uvx",
      "args": [
        "leangate"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add lambdabypi-leangate -- uvx leangate
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lambdabypi-leangate": {
      "type": "local",
      "command": [
        "uvx",
        "leangate"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lambdabypi-leangate --command uvx --arg leangate
```

### Hermes

```yaml
mcp_servers:
  lambdabypi-leangate:
    command: "uvx"
    args: ["leangate"]
```

### Netclaw

```json
{
  "McpServers": {
    "lambdabypi-leangate": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "leangate"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add lambdabypi-leangate -t stdio -c uvx -a leangate
```

### Other

```json
{
  "mcpServers": {
    "lambdabypi-leangate": {
      "command": "uvx",
      "args": [
        "leangate"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-24 (score 0, −12)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-10-23 (score 12, −13)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-10-22 (score 25, −12)

- [security improvement] Malware scan: unverified → pass

### 2026-10-21 (score 37, −13)

- [security regression] Malware scan: pass → unverified

### 2026-10-20 (score 50, −12)

- [security improvement] Malware scan: unverified → pass

### 2026-10-19 (score 62, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-18 (score 62, 0)

- [security regression] Known CVEs: pass → unverified
- [security regression] Install scripts: pass → unverified
- [security regression] Provenance: pass → fail
- [security regression] Source repository: pass → fail
- [security] The code this package runs automatically changed: its declared build backend
- [security] The attested source repository moved: lambdabypi/leangate
- [functional regression] Dependency health: 0.98 → unverified
- [functional regression] License: pass → fail
- [functional regression] Maintenance: pass → fail
- [functional] Licence: MIT
- [functional] Package version: 0.1.1 → 0.1.2

### 2026-10-17 (score 62)

First indexed and scored.

## MCP tools (7)

### `check_reuse` (~131 tokens)

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.

Input parameters:

- `code`
- `intent` (string, required)
- `repo`

### `verify_lean` (~167 tokens)

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.

Input parameters:

- `diff`
- `repo`

### `minimize` (~98 tokens)

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.

Input parameters:

- `code` (string, required)
- `findings`
- `repo`
- `tests`

### `prove_equivalent` (~80 tokens)

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.

Input parameters:

- `minimized` (string, required)
- `original` (string, required)
- `tests`

### `check_dependency` (~84 tokens)

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.

Input parameters:

- `name` (string, required)
- `purpose` (string)
- `repo`
- `version`

### `record_feedback` (~111 tokens)

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.

Input parameters:

- `accepted` (boolean, required)
- `note` (string)
- `repo`
- `signature` (string, required)

### `show_report` (~63 tokens)

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.

Input parameters:

- `repo`

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/lambdabypi-leangate/leangate#diagnostics

## Score history

- 2026-10-24: 0
- 2026-10-23: 12
- 2026-10-22: 25
- 2026-10-21: 37
- 2026-10-20: 50
- 2026-10-19: 62
- 2026-10-18: 62
- 2026-10-17: 62

## Common questions

### 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.

## Links

- PyPI project: https://pypi.org/project/leangate/
- Socket report: https://socket.dev/pypi/package/leangate
- Website: https://leangates.com/
- Changelog RSS feed: https://verifymcp.io/servers/lambdabypi-leangate/leangate.xml
- Changelog JSON feed: https://verifymcp.io/servers/lambdabypi-leangate/leangate.json
- HTML version of this page: https://verifymcp.io/servers/lambdabypi-leangate/leangate