mcpbeat Sign in

Secrets Leak Audit MCP Server

by tylerscomic-lab Your server? Claim it
answering

Secrets Leak Audit is answering right now. Last checked 4 min ago. Last commit 2 Oct 2026.

Scan text and git diffs for committed credentials using real vendor key formats plus entropy.

Uptime history 25 days of history · worst day 99%
25 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
574 ms
Response time
average over 24h
0
Stars
last commit 2 Oct 2026

Nothing serious here today

Today is the operative word: we check Secrets Leak Audit every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add secrets-leak-audit-mcp --transport http https://secrets-leak-audit-mcp.mcpize.run/mcp
Settings → Connectors → Add custom connector, then paste this address
https://secrets-leak-audit-mcp.mcpize.run/mcp
~/.codex/config.toml
[mcp_servers.secrets-leak-audit-mcp]
url = "https://secrets-leak-audit-mcp.mcpize.run/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "secrets-leak-audit-mcp": {
      "url": "https://secrets-leak-audit-mcp.mcpize.run/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "secrets-leak-audit-mcp": {
      "type": "http",
      "url": "https://secrets-leak-audit-mcp.mcpize.run/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://secrets-leak-audit-mcp.mcpize.run/mcp streamable-http sign-in 426 ms 4 min ago

Alternatives to Secrets Leak Audit

same job, measured the same way
Secret Scan
by agentic-income-bot

Check text for leaked credentials before an agent writes or commits it. Runs locally.

local only
MCP Codeaudit
by infoinlet-marketplace

Security audit for AI agents — scan code/diffs for leaked secrets, check deps via OSV.

15 installs/wk local only
VaultGuard
by evozim

Secret scanner preventing leaks of corporate keys and credentials.

1 tools answering
Secret Sentinel
by alebrito124356

Local secret guardrails: scan code, git changes and MCP configs for API keys; redact text

426 installs/wk local only
GenPark Secure Secret Token Redactor
by alphaparkinc

High-speed regex and entropy-based scanner redacting API keys, JWT tokens, and credentials

local only
Leakferret
by leakferrethq

Context-aware secret scanner: lets an AI agent scan, verify, and rewrite secrets before committing.

55 installs/wk local only
Secure Vault
by mdfifty50-boop

Encrypted secrets and credential management for agents

21 installs/wk local only
Demipass
by dustforge

Credential custody for agents: use secrets blind (ssh/http/smtp/git/db), never in context.

31 installs/wk local only

Secrets Leak Audit — questions

Answers built from our own checks of this server.

Why is there no tool list for Secrets Leak Audit?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Secrets Leak Audit working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 574 ms. The bar chart above shows every period we have measured.
How do I connect Secrets Leak Audit?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Secrets Leak Audit?
No API key is involved. Secrets Leak Audit answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Secrets Leak Audit?
It answers our handshake in 574 ms on average, which is faster than 22% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Secrets Leak Audit open source?
The code is open source: it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at secrets-leak-audit-mcp.mcpize.run, which runs on its operator's own terms.