Secrets Audit MCP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 19 Aug 2026.
Detects leaked secrets & API keys: 32+ provider rules (AWS, GitHub, Stripe, OpenAI…), zero deps.
What the code does
We read the source, 22 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const proc = spawn(python, [server], {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Secrets Audit MCP
same job, measured the same wayDetects leaked secrets (API keys, tokens, private keys) in source code.
Scans code for hardcoded secrets (AWS, Stripe, GitHub, JWTs) before an AI agent commits it.
Scan a running app or repo for leaked secrets, exposed routes and open RLS, and verify live keys
Transparent rule-based GitHub fake-star detector — LOW/MEDIUM/HIGH with per-rule evidence.
Transparent rule-based GitHub fake-star detector — LOW/MEDIUM/HIGH with per-rule evidence.
Centralized secrets manager MCP server. Generate .env files, rotate keys, sync to GitHub Actions.
Security audit for AI agents — scan code/diffs for leaked secrets, check deps via OSV.
AI security layer: code scanning, PII detection, prompt injection, secrets, CVEs
Secrets Audit MCP — questions
Answers built from our own checks of this server.