Secret Scan
io.github.agentic-income-botPublished by GitHub account agentic-income-botv1.0.0Updated Oct 24, 2026
Check text for leaked credentials before an agent writes or commits it. Runs locally.
The publisher's own server: scan.mx Email Diagnostics
Overview
A local MCP server that lets an assistant scan text for leaked credentials before it writes or commits them.
- What you can do
- Scan text for secrets with a single tool that takes content and an optional filename and returns clean or blocked with rule and line number per finding. Detect AWS access keys, GitHub, Anthropic, OpenAI, Slack, Stripe live and Google API keys, PEM private-key blocks, EVM wallet private keys, BIP39 seed phrases, and sensitive filenames such as .env, SSH keys, .pem and wallet keystores. Receive redacted previews so findings never echo the secret back into the model's context.
- When to use it
- Useful when an assistant writes files or commits code unattended and you want a check for leaked credentials before the content reaches a repository. It favors precision over recall, so commit SHAs, placeholders, environment-variable references and Stripe test keys pass clean.
- Requirements
- Runs locally over stdio as a local process; the README shows starting it with npx from the GitHub repository or by pointing the command at a cloned server.js. No authentication, environment variables or headers are declared.
Installation
In SourceWeft
- Open Secret Scan in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
mcp-secret-scan
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.
Install
Or clone and point command at node /path/to/server.js.
Tool
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.
Precision over recall, deliberately
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.
Related
agent-commit-guard— the same ruleset as a git pre-commit hook.- Hosted API:
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.
Who wrote this
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.
Source: README.md at commit 14a3aac
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Scan integrations
scan.mx Email Diagnostics
mx.scanOfficial publisher
Remote MCP server that lets an assistant run graded email deliverability and DNS checks on a domain, covering MX, SPF, DKIM, DMARC, blacklists and more.
MTG Trade Scan
fr.mtg-trade
Scans Magic: The Gathering binder photos, turning uploaded page images into processed scan jobs, with free daily pages and paid credits.
mcp-guard
Published by GitHub account diegoperezg7
Security scanner for MCP servers that checks tool lists for poisoning, shadowing, excessive permissions, leaked secrets and weak transports.
PredictionScan
Published by GitHub account JordanKarst
Derived prediction-market flow, price changes, trader research and news. 11 read-only tools.
x402-sec-scan
Published by GitHub account 6mickswagger9
Local stdio MCP server exposing an x402 paid API for AI agents, settling payments in USDC on Base through a CDP facilitator.