The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Env Secret Exposure Analyzer MCP listing page.
Your AI agent is one debug session away from leaking your secrets.
MCP server that scans your project for secret exposure risks — hardcoded API keys, unprotected .env files, and console.log calls that print credentials at runtime. Before your agent accidentally reads them out loud.
You ask your AI agent to debug a config issue. It reads src/config.ts. Inside:
The agent now has your database password in its context. It might log it, include it in a summary, or pass it to another tool. And your .env isn't in .gitignore, so the next git push will do the rest.
None of this requires the agent to be malicious. It just needs to be helpful.
env-secret-exposure-analyzer-mcp catches this before it happens. 🔐
scan_for_secretsScans source files, config files, and .env files for 20+ secret patterns. Returns file path, line number, severity, and a masked preview — never the full value.
Detects:
ghp_, gho_, ghs_)whsec_)SG.xxx), Twilio auth token + account SIDGOCSPX-)xox*)-----BEGIN ... PRIVATE KEY-----)postgres://user:pass@host)check_gitignore_coverageChecks whether sensitive files (.env, .env.local, secrets.json, private keys, certificates) are covered by .gitignore. Flags files that could be accidentally committed.
scan_for_log_leaksScans source files for console.log / logger calls that print process.env variables or objects with secret-sounding names at runtime. Catches the most common "it's just a debug line" mistakes.
A realistic .env with 20 secrets — database URLs, AWS, Stripe, Twilio, SendGrid, Google OAuth, Sentry, JWT secrets, encryption keys. Before this MCP: an AI agent reads the file, has no idea what's sensitive, and proceeds to use those values in generated code or responses.
After one scan_for_secrets call: 16 findings, all categorized by severity, all previews masked. The agent knows exactly what's dangerous before it touches anything.
"Scan this project for any secrets or API keys that might be exposed. Check if .env files are in .gitignore, and look for any console.log calls that might be leaking credentials."
The agent runs all three tools in sequence and reports a full picture: what's hardcoded, what's not protected, what's being logged.
Works great alongside:
MIT