
Env Secret Exposure Analyzer Mcp
Runs three filesystem scans to catch secrets before your AI agent sees them: hardcoded credentials across 20+ patterns (AWS keys, Stripe tokens, database URLs, JWTs), console.log statements that dump environment variables or config objects at runtime, and sensitive files missing from .gitignore. Returns masked previews with severity ratings and line numbers, never the actual values. Built for the specific risk of helpful agents accidentally ingesting credentials during debugging sessions or config reviews. Works entirely locally via stdio, no secrets leave your machine. Pairs well with CI readiness and code analysis servers if you're building pre-commit or pre-release guardrails into agent workflows.
- tools
- 3
- transport
- STDIO
- last updated
- May 20, 2026
Tools
3 toolsPublic tool metadata for what this MCP can expose to an agent.
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.
Scans 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.
No parameter schema in public metadata yet.
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.
Checks whether sensitive files (.env, .env.local, secrets.json, private keys, certificates) are covered by .gitignore. Flags files that could be accidentally committed.
No parameter schema in public metadata yet.
scan_for_log_leaksScans source files for console.log / logger calls that print process.env variables or objects with secret-sounding names at runtime.
Scans source files for console.log / logger calls that print process.env variables or objects with secret-sounding names at runtime.
No parameter schema in public metadata yet.
Sponsors
Readme
π env-secret-exposure-analyzer-mcp
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.
π€ The problem
You ask your AI agent to debug a config issue. It reads src/config.ts. Inside:
console.log('Config loaded:', JSON.stringify(config));
console.log(process.env.DATABASE_PASSWORD);
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.
Details
- Repository
- github.com/vola-trebla/env-secret-exposure-analyzer-mcp
- Package
env-secret-exposure-analyzer-mcp- Transport
- STDIO
- Registry
- MCP registry, active
More from vola-trebla
- Flakiness Knowledge Graph Mcp
- Ndjson Local Log Triage Mcp
- Playwright Network Chaos Mcp
- Playwright Spatial Layout Mcp
- Sourcemap Retrace Mcp
- Tailwind Context Resolver Mcp
- Tsconfig Inheritance Flattener Mcp
- V8 Cpu Profile Decoder Mcp
- Release Readiness Triage Mcp
- React Render Profile Mcp2
- Playwright Trace Decoder Mcp1
- Ast Impact Mapper Mcp