Log inSubmit server
Leakferret logo

Leakferret

Scans repositories for secrets, verifies live credentials, and gives coding agents rewrite proposals over MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Leakferret

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "leakferret": {
      "command": "npx",
      "args": [
        "-y",
        "@leakferret/mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @leakferret/mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 12d ago.

Overview

The leakferret MCP server lets coding agents scan local repositories for hardcoded secrets, classify findings, verify credentials with providers, and propose environment-variable rewrites. It runs as a local JSON-RPC process over stdio, so secret values remain on the developer’s machine while provider checks go directly to the provider. Reach for it when an agent needs to inspect changes before committing, distinguish live credentials from fixtures, or compare findings against a baseline.

Use cases

  • Scan agent-generated code before committing
  • Verify whether detected credentials are live
  • Propose environment-variable rewrites for hardcoded secrets
  • Compare repository findings against a baseline
  • Inspect secret patterns and verification providers

Key features

  • Repository scanning across 60+ secret types
  • Provider-backed live credential verification
  • Fixture and placeholder classification
  • Environment-variable rewrite proposals
  • Baseline comparison using HMAC fingerprints
  • Read-only secret-type and verifier resources

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

11/11 checks healthy over the last 57d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · @leakferret/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars4Stargazers on the source repository.
npm downloads244Package downloads in the last 30 days.
Last commit2mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.

How Leakferret works

What leakferret MCP server does

The leakferret MCP server exposes leakferret’s local secret-scanning engine to coding agents. It checks repository files for more than 60 secret patterns, including dotfiles such as .env, while respecting .gitignore. A separate option can scan Git history rather than only the working tree.

The server supports a workflow that moves from detection to decision and remediation. Candidates can be classified as real, fixture, or unknown; known public examples and dummy values can therefore be excluded from actionable results. Provider verification can then determine whether a credential is live. Rewrite proposals replace hardcoded literals with language-appropriate environment-variable lookups and can include an .env.example entry and secret-manager seed commands.

How it works

The MCP process runs locally and communicates with the agent using JSON-RPC over stdio. The raw secret is kept on the local machine. Reports, logs, and network messages contain only redacted previews, while provider verification calls go directly from the machine to the relevant provider.

Five MCP tools cover the main workflow:

  • scan_repository finds candidate secrets in a repository.
  • classify_candidates assigns classifications using offline rules and heuristics, with model-assisted classification available through the supplied prompt.
  • verify_finding makes a provider check to determine whether a finding is live.
  • propose_rewrite prepares an environment-variable rewrite for a hardcoded value.
  • baseline_diff compares findings with a baseline containing one-way HMAC fingerprints, allowing CI to focus on new findings.

The engine natively verifies credentials for roughly 25 providers, including AWS, GitHub, GitLab, Stripe, OpenAI, Anthropic, Slack, Twilio, SendGrid, and others listed by the project. A trufflehog binary can provide fallback verification for additional credential types.

Setup and configuration

Run the packaged MCP launcher with npx @leakferret/mcp, then register it under mcpServers. A native leakferret binary can instead be started with the mcp argument. Claude Desktop, Cursor, Continue, and Claude Code are shown as supported configuration targets in the project documentation. Claude Code can use a project-level .mcp.json file or its claude mcp add command.

The optional LEAKFERRET_BIN environment variable points wrappers at a local binary, which is useful for offline or development installations. No server-side account or separate verification service is described. The provider APIs receive verification requests directly from the local machine.

Tools and capabilities

In addition to tools, the leakferret MCP server provides a classify prompt for inline model-assisted classification. Two read-only resources expose the bundled engine metadata: leakferret://secret-types lists detectable patterns, and leakferret://verifiers lists live-verification providers.

The server is a fit for agent-driven development workflows where generated code may introduce credentials. It can help an agent inspect a repository, verify whether a candidate is active, suggest a safe environment lookup, and identify newly introduced findings through a baseline.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Leakferret

leakferret is an MCP server that connects an AI coding agent to local repositories and provider APIs for secret checks. Its main tools are scan_repository, classify_candidates, verify_finding, propose_rewrite, and baseline_diff, with a classify prompt and read-only catalog resources over stdio.

Install it with `npx @leakferret/mcp`, then add that command to the client's `mcpServers` configuration. If you use the native binary, start it with `leakferret mcp` instead. The project also documents Claude Code's `claude mcp add` command.

Yes, Cursor is named as a supported configuration target. Register the stdio command `npx @leakferret/mcp` under the `leakferret` MCP server entry, or point the configuration at a native binary using the `mcp` argument.

Yes, `verify_finding` can check whether a credential is live through a supported provider. Native verification covers roughly 25 providers, and a trufflehog binary can provide fallback verification for other credential types.

No, the raw secret stays on the local machine. Provider verification requests go directly from that machine to the provider, and reports, logs, and network messages use only redacted previews.

Related MCP servers

All in Security All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewLeakferret AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/leakferret?style=directory)](https://allmcps.com/mcp/leakferret)
HTML Embed
<a href="https://allmcps.com/mcp/leakferret"><img src="https://allmcps.com/api/badge/leakferret?style=directory" alt="Leakferret on AllMCPs" /></a>