env-secret-exposure-analyzer-mcp
Identifies exposed Datadog API keys in project files to prevent accidental leakage.
Scans for unprotected .env files and checks gitignore coverage to prevent accidental exposure of environment variables.
Detects exposed GitHub tokens (e.g., ghp_, gho_, ghs_) in source files and environment files to prevent accidental leakage.
Identifies exposed Google API keys and OAuth client secrets in project files to prevent accidental leakage.
Detects exposed OpenAI API keys in source files and environment files to prevent accidental leakage.
Identifies exposed SendGrid API keys (SG.xxx) in project files to prevent accidental leakage.
Detects exposed Sentry DSNs in source files and environment files to prevent accidental leakage.
Identifies exposed Slack tokens (xox*) in project files to prevent accidental leakage.
Detects exposed Stripe secret/publishable keys and webhook secrets in source files and environment files to prevent accidental leakage.
Identifies exposed Twilio auth tokens and account SIDs in project files to prevent accidental leakage.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@env-secret-exposure-analyzer-mcpscan this project for secret exposure risks"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
π 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.
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. π
Related MCP server: mcp-sanity-check
π οΈ 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 SIDGoogle 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
Secret Scan Results
Project: /project
Files scanned: 24
Findings: 5
[CRITICAL] .env:3 β AWS Access Key
Preview: AKIA****MPLE
[CRITICAL] .env:7 β Database URL with password
Preview: post****sswd
[CRITICAL] src/auth.ts:12 β Hardcoded JWT secret
Preview: my-s****ecret
[HIGH] .env:14 β Hardcoded session secret
Preview: sess****key!
[MEDIUM] .env:28 β Sentry DSN
Preview: http****7890check_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.
Gitignore Coverage Check
Project: /project
β .env β Add to .gitignore: .env
β .env.local β Add to .gitignore: .env.local
β secrets.jsonscan_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.
Log Leak Scan
Project: /project
Files scanned: 18
Findings: 3
[CRITICAL] src/config.ts:8
console.log("Config loaded:", JSON.stringify(config));
[HIGH] src/server.ts:42
console.log(process.env.AWS_SECRET_ACCESS_KEY);
[HIGH] src/db.ts:15
logger.info({ password: dbConfig.password });π§ͺ 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
{
"mcpServers": {
"secret-scanner": {
"command": "npx",
"args": ["-y", "env-secret-exposure-analyzer-mcp"]
}
}
}π 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
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityCmaintenanceScans code for exposed secrets, API keys, tokens, and credentials across 69 patterns covering cloud services, AI platforms, payment providers, authentication services, and databases.Last updatedMIT
- Flicense-qualityCmaintenanceScans repositories for owner identifiers and secrets, blocking pushes or CI merges if any are found.Last updated
- AlicenseAqualityBmaintenanceEnables scanning diffs or code blobs for leaked secrets, returning a verdict with severity and masked findings, all processed locally with no data sent externally.Last updated1MIT
- Alicense-qualityBmaintenanceA keyless, defensive code-security auditor that scans codebases for hardcoded secrets, audits dependencies for known CVEs, and checks passwords against breach data using k-anonymity.Last updated1MIT
Related MCP Connectors
Compliance & security scan for your app: secrets, exposed files, headers, privacy, AI-disclosure.
Screens public GitHub repos and PRs to generate risk maps, findings, and merge-readiness signals.
Multi-CI security scanner with a live threat-intel feed of compromised CI components
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/vola-trebla/env-secret-exposure-analyzer-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server