Leakferret MCP Server

MCP-native secret scanner - verified findings, agent-applied rewrites. leakferret is one fast Rust binary that is engine, CLI, and MCP server. It finds hardcoded secrets in your code, calls the provider to confirm which ones are actually live, and rewrites the leak in place to read from an environment variable. It runs in your terminal, in CI, and as a tool your coding agent calls before it commits - and the raw…

People connecting security tools to Claude, Cursor, VS Code, or another MCP client. The project is written in Rust.

VERIFIED ACTIVE

LAST COMMIT 2026-07-25 · ★ 5 · #89 OF 182 MAINTAINED SECURITY · VERIFIED 2026-08-25

MIT · Rust servers · how we verify → /methodology

01 · Install Leakferret

before you install - you'll need

Set STRIPE_SECRET_KEY, GITHUB_TOKEN, SENDGRID_API_KEY, ADMIN_PASSWORD, AWS_ACCESS_KEY_ID before connecting.

Claude Code

claude mcp add leakferrethq-leakferret -- npx -y @leakferret/mcp

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "leakferrethq-leakferret": {
      "command": "npx",
      "args": [
        "-y",
        "@leakferret/mcp"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license MIT - declared in the repository

npm package @leakferret/mcp - the @leakferret scope differs from the repo owner (leakferrethq); confirm it's the project's official package

registry namespace io.github.leakferrethq is GitHub-verified and matches the repo owner

03 · What Leakferret can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

Latest releases

v0.1.9 · 2026-06-03

All notable changes to this project will be documented in this file. · The format is based on Keep a Changelog, · and this project adheres to Semantic Versioning. · [0.1.9] - 2026-06-03 · Added · leakferret org…

v0.1.8 · 2026-06-03

All notable changes to this project will be documented in this file. · The format is based on Keep a Changelog, · and this project adheres to Semantic Versioning. · [0.1.8] - 2026-06-03 · Added · MCP server now exposes…

v0.1.7 · 2026-06-02

All notable changes to this project will be documented in this file. · The format is based on Keep a Changelog, · and this project adheres to Semantic Versioning. · [0.1.7] - 2026-06-03 · Added · Detection for ~28 more…

04 · Who maintains Leakferret

leakferret is maintained by leakferrethq. It's the only MCP server we track from this author; the repo dates to May 2026.

05 · Facts

category
security - ranked #89 of 182 actively-maintained security servers as of 2026-08-25.
release cadence
9 releases in the last 90 days (latest 2026-06-03)
registry
io.github.leakferrethq/leakferret (active, first published 2026-06-01 · 4 versions)
packages
npm:@leakferret/mcp

06 · Leakferret FAQ

What is Leakferret?

MCP-native secret scanner - verified findings, agent-applied rewrites. leakferret is one fast Rust binary that is engine, CLI, and MCP server. It finds hardcoded secrets in your code, calls the provider to confirm which ones are actually live, and rewrites the leak in place to read from an environment variable. It runs in your terminal, in CI, and as a tool your coding agent calls before it commits - and the raw…

Is Leakferret still maintained?

Yes - as of 2026-08-25, its last commit was 2026-07-25 and it shipped 9 releases in the last 90 days. We re-verify nightly.

How do I install Leakferret?

Run `npx -y @leakferret/mcp`. The README documents 5 environment variables (STRIPE_SECRET_KEY, GITHUB_TOKEN, SENDGRID_API_KEY…) to set first. Set STRIPE_SECRET_KEY, GITHUB_TOKEN, SENDGRID_API_KEY, ADMIN_PASSWORD, AWS_ACCESS_KEY_ID before connecting. You can also paste the ready-made client config above.

Does Leakferret run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to Leakferret