io.github.lambdabypi/leangate

{
  "mcpServers": {
    "leangate": {
      "command": "uvx",
      "args": [
        "leangate==0.1.2",
        "mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "leangate": {
      "command": "uvx",
      "args": [
        "leangate==0.1.2",
        "mcp"
      ]
    }
  }
}

{
  "servers": {
    "leangate": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "leangate==0.1.2",
        "mcp"
      ]
    }
  }
}

code --add-mcp '{"name":"leangate","type":"stdio","command":"uvx","args":["leangate==0.1.2","mcp"]}'

claude mcp add --transport stdio leangate -- uvx leangate==0.1.2 mcp

npx @modelcontextprotocol/inspector@2.11.0 -- uvx leangate==0.1.2 mcp

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Facts about the publisher. We do not turn them into a trust score.

Source: the registry entry and api.github.com · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

• io.github.morluto/reaREAcompare with this one
• io.github.thedaviddias/front-end-checklistFront-End Checklistcompare with this one
• io.github.ruvnet/claude-flowcompare with this one
• io.github.ChromeDevTools/chrome-devtools-mcpChrome DevTools MCPcompare with this one
• io.github.secforge/chrome-devtools-mcpChrome DevTools MCPcompare with this one
• io.github.DeusData/codebase-memory-mcpCodebase Memorycompare with this one

Active servers whose topic is also “developer-tools”, most GitHub stars first. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

No session

No session could be opened when we tried, so no check could run. No security score is given; a check we did not run is never counted as passed.

Why not security-tested: The package's process closed before a session opened, and the recorded output does not show whether the cause was ours or the package's. — cause not determined

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). None of the 18 checks that apply to it could be exercised. We do not publish security-check outcomes for named servers.

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

The steps in order, as the test record holds them.

1. 0 msStarted the published package in an isolated sandbox
2. No session could be opened.
3. 342 msFinished: 0 checks exercised.

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.