How do I install Secrets Leak Audit?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Secrets Leak Audit need an API key?

No required environment variable is listed on this record.

What transport does Secrets Leak Audit use?

Secrets Leak Audit is reached over HTTP.

When was Secrets Leak Audit last checked?

Last checked 2026-11-10. Scan text and git diffs for committed credentials using real vendor key formats plus entropy.

Secrets Leak Audit MCP server

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://secrets-leak-audit-mcp.mcpize.run/mcp

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

1claude mcp add --transport http io.github.tylerscomic-lab-secrets-leak-audit-mcp https://secrets-leak-audit-mcp.mcpize.run/mcp

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.tylerscomic-lab-secrets-leak-audit-mcp": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://secrets-leak-audit-mcp.mcpize.run/mcp"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Live

Transport: http
Version: 1.0.0
Last checked

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

secrets-leak-audit-mcp

An MCP server that scans text and diffs for accidentally-committed credentials — the single most common "oops" in software, and an easy thing for an AI coding agent to introduce without noticing (pasting a working example that includes a real key, or writing a test fixture with a plausible-looking but real value).

What it catches

High-precision vendor key matches. Real, current (2026) structural formats for AWS access keys, GitHub PATs (classic and fine-grained), Stripe live keys, Slack tokens, Google API keys, OpenAI and Anthropic keys, npm tokens, SendGrid, Twilio, PEM private key blocks, JWTs, and database connection strings with embedded credentials. These are precise format matches, not guesses — an AWS key is AKIA/ASIA + 16 specific characters, not "looks like it might be a key."

Entropy-based fallback. For secret-shaped variable names (API_KEY, PASSWORD, *_TOKEN) with no recognized vendor prefix, checks the assigned value's character-randomness (Shannon entropy). A real generated credential and "password123" both match a suspicious name, but only one has the entropy of an actual secret — flagged separately and at lower confidence than the vendor-format matches, since this one really is a heuristic.

Every match is redacted before it's returned — the tool never echoes a full secret value back, even to confirm a hit.

Tools

scan_for_secrets

Scans any text (a file's contents, a config snippet) for both categories above.

scan_diff

Scans a unified git diff and only checks lines the diff actually adds — won't flag a secret that was already being removed in the same diff, or one that only appears in unchanged context lines.

Use it

Hosted (recommended): MCPize — free tier, $7/mo Pro.

Self-host:

npm install node server.js

Part of a small suite

License

MIT

Secrets Leak Audit

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Secrets Leak Audit?

Does Secrets Leak Audit need an API key?

What transport does Secrets Leak Audit use?

When was Secrets Leak Audit last checked?

Documentation