Secrets Audit MCP server
Detects leaked secrets & API keys: 32+ provider rules (AWS, GitHub, Stripe, OpenAI…), zero deps.
1 stars
Reviews
Write oneNobody has reviewed Secrets Audit yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Secrets Audit tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 39 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Secrets Audit compares
Against every graded E-commerce MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 80/100
- higher than 70% of 2,174 E-commerce servers
- GitHub stars
- 1
- more than 65% of 1,047 E-commerce servers
Install Secrets Audit in Claude Code, Cursor or VS Code
claude mcp add secrets-audit-mcp -- docker run -i --rm ghcr.io/eltociear/secrets-audit-mcp:1.0.1
What the publisher says
From the Secrets Audit repository's README, as published. We do not edit it. Read it on GitHub
secrets-audit-mcp
MCP server that detects leaked credentials in source code. Zero dependencies. Single file.
Detects API keys, OAuth tokens, private keys, webhooks, and crypto wallet secrets across 30+ providers (AWS, GCP, GitHub, Stripe, OpenAI, Anthropic, Slack, Discord, Telegram, Twilio, SendGrid, Heroku, DigitalOcean, npm, HuggingFace, Replicate, Cloudflare, and more).
Companion to skill-audit-mcp (behavioral patterns) — together they cover secrets + behaviors in one MCP toolchain.
Why
Most secret scanners are giant Go binaries (trufflehog, gitleaks). This is a 500-line Python file that runs as an MCP stdio server, so any LLM agent (Claude Desktop, Cursor, Windsurf, Cline) can ask it scan_directory and get a structured report in their tool-call response.
Use cases:
- Pre-commit hook in CI
- Agent-driven code review ("did this PR leak credentials?")
- Audit a freshly-cloned repo before opening it in your shell
- Inline scan during agent file edits
Install
# Python (recommended)
git clone https://github.com/eltociear/secrets-audit-mcp.git
python3 secrets-audit-mcp/server.py # stdio MCP server
# Or via npm wrapper (TBD)
npm install -g @eltociear/secrets-audit-mcpMCP client config
{
"mcpServers": {
"secrets-audit": {
"type": "stdio",
"command": "python3",
"args": ["/path/to/secrets-audit-mcp/server.py"]
}
}
}Tools
All return a risk score (0-100), severity bucket (CRITICAL/HIGH/MEDIUM/LOW/SAFE), and per-finding details with line numbers and redacted matches.
Coverage
Providers (32 rules total):
- Cloud: AWS access/secret, GCP API key + service-account JSON, Heroku, DigitalOcean, Cloudflare
- Source/CI: GitHub PAT/OAuth/App/Refresh/Fine-grained, npm tokens, Docker Hub PAT
- Payments: Stripe secret + restricted
- Comms: Slack bot/user/webhook, Discord bot/webhook, Telegram bot, Twilio, SendGrid, Mailgun
- AI/ML: OpenAI, Anthropic, HuggingFace, Replicate
- Web3: Ethereum private key (context-aware), Alchemy, Infura
- Keys: RSA / EC / OpenSSH / PGP / generic PEM private keys
- Generic: JWT, apikey="..." heuristic, generic secret assignments
Each match is redacted (AKIA***MPLE) before being returned, so the report itself doesn't leak the secret to the next LLM hop.
CI usage
- name: Secrets audit
run: |
python3 server.py <<EOF | jq -r '.result.content[0].text'
{"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"scan_directory","arguments":{"path":"."}}}
EOFA first-class GitHub Action will ship as eltociear/secrets-audit-action@v1.
Sister project — skill-audit-mcp
skill-audit-mcp covers behavioral malware patterns (download-and-execute, prompt injection, credential exfiltration). Run both for full coverage:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Secrets Audit: common questions
- Is Secrets Audit MCP server safe?
- Mostly: it is graded B (80/100). Read the Secrets Audit safety report
- How do I install Secrets Audit?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Secrets Audit need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Secrets Audit maintained?
- The last commit was 77 days ago (2026-08-19). The latest release is v1.0.1.
- What can I use instead of Secrets Audit?
- Servers from other publishers that do the same job: Webhook Toolkit MCP server, Idea Reality MCP server and Stripe MCP server.
- How does Secrets Audit compare with other E-commerce MCP servers?
- safety score 80/100 (higher than 70% of 2,174 E-commerce servers); github stars 1 (more than 65% of 1,047 E-commerce servers). Full comparison.
Alternatives to Secrets Audit
Same job from other publishers: the closest match first, then the best rated.
Webhook ToolkitWebhook URLs for AI agents: receive, wait for, replay, sign and verify webhooks (Stripe, GitHub…).not reviewedGrowingA- Idea RealityPre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.not reviewedEstablishedB
- StripeMCP server integrating with Stripe - tools for customers, products, payments, and more.not reviewedEstablishedA
- Polymarket ToolkitRead-only Polymarket data tools for AI agents: profiles, PnL, market scans. No keys, no orders.not reviewedEstablishedB
- ShopwareQuery and safely manage a Shopware 6 shop: products, orders, customers, stock, audits, reports.not reviewedGrowingB