secretscan
Detects AWS access key IDs and secret keys in scanned text to prevent leaking Amazon Web Services credentials.
Detects GitHub personal access tokens and fine-grained tokens in scanned text to prevent leaking GitHub credentials.
Detects Google API keys (AIza...) in scanned text to prevent leaking Google Cloud credentials.
Detects npm publish tokens (npm_...) in scanned text to prevent leaking npm registry credentials.
Detects Slack tokens (e.g., xoxb-... ) in scanned text to prevent leaking Slack credentials.
Detects Stripe live and test secret keys in scanned text to prevent leaking Stripe API credentials.
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., "@secretscanscan this diff for leaked secrets"
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.
secretscan-mcp-server
An MCP server that scans a diff, a file's contents, or a pasted snippet for accidentally-committed secrets -- so any MCP-compatible agent can self-check its own changes before committing, opening a PR, or pasting a log excerpt anywhere. Fully local: no API key, no network call, no dependency beyond the MCP SDK and Zod.
Why
A leaked credential is one of the most common real-world causes of account
and infrastructure compromise, and one of the easiest mistakes to make in a
large diff -- a debug console.log with a real API key, a config file
committed by accident, a .env pasted into a chat while asking for help.
An agent that's about to commit, push, or share text is well positioned to
catch this before it happens, if it has a cheap way to check.
Related MCP server: opzyai
Tool
scan_for_secrets
Scans text against a fixed set of provider-format signatures plus a generic, entropy-gated heuristic:
Detector | Catches |
| AWS access key IDs ( |
| AWS secret keys, when contextually labeled |
| GitHub PATs ( |
| Slack tokens ( |
| Stripe secret/publishable keys |
| Google API keys ( |
| npm publish tokens ( |
| PEM private key blocks |
| JSON Web Tokens |
| anything assigned to a secret-sounding variable name ( |
Findings are always redacted -- AKIAIOSFODNN7EXAMPLE is reported as
AKIA************MPLE (20 chars), never in full. The tool's own output is
therefore safe to log or display without further propagating whatever it
found.
This is a fixed-pattern + heuristic scan, not exhaustive. A clean result means "no known pattern matched," not "definitely safe" -- the in-app output says so explicitly.
Install and configure
git clone https://github.com/wedo911/secretscan-mcp-server.git
cd secretscan-mcp-server
npm install
npm run buildAdd it to your MCP client's config (e.g. claude_desktop_config.json, or a
project's .mcp.json for Claude Code):
{
"mcpServers": {
"secretscan": {
"command": "node",
"args": ["/absolute/path/to/secretscan-mcp-server/dist/index.js"]
}
}
}Run the tests
npm run build
node --test tests/entropy.test.mjs tests/detectors.test.mjs24 tests, including one for every named detector, the placeholder- and low-entropy-filtering behavior of the generic detector, and an explicit check that redacted output never contains the full secret value.
Try it without a client
npx @modelcontextprotocol/inspector --cli node dist/index.js \
--method tools/call --tool-name scan_for_secrets \
--tool-arg text='aws_access_key_id = AKIAIOSFODNN7EXAMPLE'(That's AWS's own publicly documented example key -- not a real credential.)
License
MIT — see LICENSE.
Maintenance
Tools
Related MCP Servers
- 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.1MIT
- AlicenseNot gradedqualityBmaintenanceLocal-first security check for AI coding agents — finds hardcoded secrets, exposed .env files, git-history leaks and vulnerable dependencies (OSV), entirely on your machine. Ask your agent "is this safe to ship?" and get a Launch Readiness score with a fix for every finding.MIT
- AlicenseNot gradedqualityAmaintenanceScans text and files for common secrets (AWS, GitHub, etc.) and redacts them to prevent credential leakage in AI-assisted development. Runs entirely locally with no telemetry.MIT
- AlicenseAqualityDmaintenanceScans projects for hardcoded secrets, unprotected .env files, and console.log leaks to prevent credential exposure.544MIT
Related MCP Connectors
Risk-scan a diff, flag AI-generated-code tells, find secrets. 5 of 7 tools need no account.
Generate SBOMs, scan vulnerabilities, and analyze dependencies from local projects or Git repos.
Screens public GitHub repos and PRs to generate risk maps, findings, and merge-readiness signals.
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/wedo911/secretscan-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server