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 "Deploy 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., "@secretscan scan 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: netallion-mcp-lite
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.
Available Tools
1 toolscan_for_secretsScan Text for Leaked SecretsARead-onlyIdempotent
Scan text (a git diff, a file's contents, a pasted snippet) for accidentally-committed secrets: cloud provider keys (AWS, Google), platform tokens (GitHub, Slack, npm), payment keys (Stripe), private key blocks, JWTs, and a generic entropy-gated check for anything assigned to a secret-sounding variable name. Use this before committing, opening a PR, or pasting logs/config anywhere -- a committed secret is one of the most common real-world causes of account and infrastructure compromise, and is easy to miss in a large diff.
Findings are always redacted (first/last few characters only) -- this tool never returns a full secret value, so its own output is safe to log or display.
Args:
text (string, 1-200000 chars): the text to scan.
Returns: For JSON format: { "found": boolean, "riskLevel": "none" | "medium" | "high" | "critical", "findings": [ { "detector": string, "category": string, "severity": "low"|"medium"|"high"|"critical", "line": number, "column": number, "redacted": string } ] }
Examples:
Use when: about to run "git commit" or "git push" -- scan the staged diff first
Use when: about to paste a config file, log excerpt, or error message into a chat or issue tracker
Don't use when: you need certainty nothing sensitive is present -- this is a fixed-pattern + heuristic scan, not exhaustive; a clean result means "no known pattern matched," not "definitely safe"
Error Handling:
Returns an error if text is empty or exceeds 200000 characters.
Inputs: text (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
Only one tool exists, so there is zero ambiguity or risk of misselection. The tool's purpose is clearly singular.
The single tool uses a consistent verb_noun pattern ('scan_for_secrets'), which is clear and predictable.
With only one tool, the server feels thin, but for a narrow purpose like scanning text for secrets, a single comprehensive tool is reasonable. It borders on minimal but works.
The tool covers the full scanner domain: it detects a wide variety of secrets, provides redacted output, and handles error cases. There are no obvious missing operations for its stated purpose.
Maintenance
Related MCP Connectors
Scan configs, files, or text for leaked secrets and obvious misconfigurations. Nothing stored.
Scan text and git diffs for committed credentials using real vendor key formats plus entropy.
Checks AI-written code for leaked keys and made-up packages, on your machine. Never uploads code.
Deep security scans of repos you own from your editor: dependency CVEs, SAST, git-history secrets.
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 gradedqualityCmaintenanceScans 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.572 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to scan source code for secrets like API keys and passwords locally without network requests.2Apache 2.0