
Env Secret Exposure Analyzer Mcp
io.github.vola-treblaPublished by GitHub account vola-treblav0.2.0Updated Oct 24, 2026
Scans projects for secret exposure: leaked API keys, unprotected .env files, and secrets in logs.
Overview
Local MCP server that scans a project for exposed secrets — hardcoded API keys, unprotected .env files and credential-printing log calls — with masked previews.
- What you can do
- Scan source, config and .env files for 20+ secret patterns (cloud, payment, chat, AI provider keys, private keys, database URLs), returning path, line, severity and a masked preview
- Check whether sensitive files such as .env, secrets.json, private keys and certificates are covered by .gitignore
- Scan source files for console.log or logger calls that print environment variables or secret-named objects
- Report findings grouped by severity so the assistant can summarize exposure risks before touching the code
- When to use it
- Useful when an assistant works inside a codebase and may read config or environment files, and you want a pre-flight check of what is hardcoded, unignored or logged before secrets end up in the model's context or a commit.
- Requirements
- Runs locally over stdio, started with npx from the npm package env-secret-exposure-analyzer-mcp, so Node.js and network access for the first install are needed. No authentication, environment variables or headers are declared. Desktop only.
Installation
In SourceWeft
- Open Env Secret Exposure Analyzer Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
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:
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. 🔐
🛠️ Tools
scan_for_secrets
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.
Detects:
- AWS access keys + secret keys
- GitHub tokens (
ghp_,gho_,ghs_) - Stripe secret/publishable keys + webhook secrets (
whsec_) - Anthropic, OpenAI API keys
- SendGrid (
SG.xxx), Twilio auth token + account SID - Google API keys + OAuth client secrets (
GOCSPX-) - Slack tokens (
xox*) - Private keys (
-----BEGIN ... PRIVATE KEY-----) - Database URLs with embedded credentials (
postgres://user:pass@host) - JWT secrets, session secrets, encryption keys
- Sentry DSN, Datadog API key
- Generic hardcoded passwords, secrets, tokens
check_gitignore_coverage
Checks 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_leaks
Scans 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.
🧪 What it looks like in practice
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.
⚡ Setup
🚀 Usage
"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:
- tsconfig-inheritance-flattener-mcp — for TypeScript config analysis
- release-readiness-triage-mcp — for CI triage before release
- ast-impact-mapper-mcp — for code→test correlation
📦 Links
- npm: npmjs.com/package/env-secret-exposure-analyzer-mcp
- GitHub: github.com/vola-trebla/env-secret-exposure-analyzer-mcp
License
MIT
Source: README.md at commit 5c1970f
Tools
0Version history
1- v0.2.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts