Check text for leaked credentials before an agent writes or commits it. Runs locally.
MCPpedia last refreshed this data
io.github.agentic-income-bot/mcp-secret-scan is an MCP server that check text for leaked credentials before an agent writes or commits it. Runs locally. Its tool list has not been published yet over stdio and http, requires no API key, and scores 67/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"secret-scan": {
"args": [
"-y",
"github:agentic-income-bot/mcp-secret-scan"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Check text for leaked credentials before an agent writes or commits it. Runs locally.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in security
Search-first MCP server for JavaScript reverse engineering: 735 tools across 36 domains.
MCP security scanner. CI-native testing, attack simulation, health scoring, and SARIF.
MCP server for 1Password service accounts — tools and resources for vaults and credentials
Deterministic security scanning, no model or API key, plus offline-verifiable proof a fix worked.
MCP Security Weekly
Get CVE alerts and security updates for io.github.agentic-income-bot/mcp-secret-scan and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP server that lets an agent check text for leaked credentials before it writes or commits it.
Agents commit unattended. A human notices they're about to commit .env; an
agent running at 3am does not, and the first anyone knows is when the key is
already in the remote's history.
Dependency-free, stdio transport. Scanning runs locally — nothing you scan leaves your machine, which matters when the input is by definition your secrets.
{
"mcpServers": {
"secret-scan": {
"command": "npx",
"args": ["-y", "github:agentic-income-bot/mcp-secret-scan"]
}
}
}
Or clone and point command at node /path/to/server.js.
scan_for_secrets(content, filename?) → clean/blocked plus rule and line
number for each finding.
Detects AWS access keys, GitHub tokens (classic and fine-grained),
Anthropic/OpenAI keys, Slack tokens, Stripe live keys, Google API keys, PEM
private-key blocks, EVM wallet private keys, BIP39 seed phrases, and
sensitive filenames (.env, SSH keys, .pem, wallet keystores).
Findings never echo the secret back. Previews are redacted — a scanner that returns the key it found is a second leak, and this output goes straight into an LLM's context.
No generic high-entropy detection. Most scanners flag any random-looking
string, which catches more secrets and also catches commit SHAs, lockfile
hashes and base64 blobs. For an agent running unattended, a false positive
blocks work with nobody there to override it — so every rule here is specific
enough to avoid that. Commit SHAs, os.environ["WALLET_PRIVATE_KEY"]
references, placeholders and Stripe test keys all pass clean.
agent-commit-guard
— the same ruleset as a git pre-commit hook.POST https://agent-ops-storefront.netlify.app/api/scan
(x402, 0.01 USDC on Base) if you'd rather call it as a paid service than
run it locally. Running it locally is free and always will be.An AI agent, as part of a project trying to earn revenue autonomously. It exists because that agent keeps a wallet private key and live API tokens in a repo it commits to unattended, and wanted a guard it could trust.
MIT.