Env Secret Exposure Analyzer MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 57 installs a week from npm. Last commit 20 May 2026.
Scans projects for secret exposure: leaked API keys, unprotected .env files, and secrets in logs.
What the code does
We read the source, 2 d ago · rules 995398eba69f
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 fullPath = path.join(repoPath, relFile);
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.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add env-secret-exposure-analyzer-mcp -- npx -y env-secret-exposure-analyzer-mcp{
"mcpServers": {
"env-secret-exposure-analyzer-mcp": {
"command": "npx",
"args": [
"-y",
"env-secret-exposure-analyzer-mcp"
]
}
}
}[mcp_servers.env-secret-exposure-analyzer-mcp]
command = "npx"
args = ["-y", "env-secret-exposure-analyzer-mcp"]{
"mcpServers": {
"env-secret-exposure-analyzer-mcp": {
"command": "npx",
"args": [
"-y",
"env-secret-exposure-analyzer-mcp"
]
}
}
}{
"servers": {
"env-secret-exposure-analyzer-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"env-secret-exposure-analyzer-mcp"
]
}
}
}Alternatives to Env Secret Exposure Analyzer MCP
same job, measured the same wayScan and monitor websites for leaked keys, exposed files, security headers, SEO issues and uptime.
Projects, estimates, daily logs and invoices in Contractor Foreman.
A managed runtime for custom API integrations. Manage lines, endpoints, keys, logs and DLQ via MCP.
iptables for MCP — blocks dangerous tool calls, scans for secrets, logs everything.
Start and stop timers, log time entries, and read projects, tasks and time entries in solidtime.
Secrets vault for Claude Code with audit logs, access rules, and AES-256 encryption.
Track time in Clockify: time entries, projects, clients, tags and reports; start, stop and log time.
Read-only Kubernetes MCP server: inspect resources, logs, events, and metrics. Secrets are masked.
Env Secret Exposure Analyzer MCP — questions
Answers built from our own checks of this server.