mcpField
S
secrets-audit-mcp

secrets-audit-mcp

Local
github.com/eltociearSecurity1Updated 10w ago

About secrets-audit-mcp

secrets-audit-mcp is an MCP server for finding exposed credentials in source code, suited to code review and CI checks. It scans text, individual files, or directories and reports risk levels and finding locations with matches redacted.

Key features

  1. 01Scan text, files, and directories
  2. 02Cover 32 credential rule types
  3. 03Scan recursively and skip common directories
  4. 04Return risk scores and severity levels
  5. 05Show line numbers and redact matches
  6. 06Zero-dependency, single-file implementation

Use cases

  1. 01Check a codebase before committing
  2. 02Review changes for leaked credentials
  3. 03Scan a cloned repository before opening it
  4. 04Run checks during agent file edits

MCP support

The MCP server gives MCP clients tools to scan text, files, and directories, returning structured risk reports. Matches are redacted in the output.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"eltociear-secrets-audit": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/eltociear/secrets-audit-mcp:1.0.1"
]
}
}
}
Run commanddocker run -i --rm ghcr.io/eltociear/secrets-audit-mcp:1.0.1

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
ocighcr.io/eltociear/secrets-audit-mcp:1.0.1

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

secrets-audit-mcp

smithery badge MCP Registry

MCP server that detects leaked credentials in source code. Zero dependencies. Single file.

License: MIT Python 3.6+ MCP Sister: skill-audit-mcp

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-mcp
MCP client config
{
  "mcpServers": {
    "secrets-audit": {
      "type": "stdio",
      "command": "python3",
      "args": ["/path/to/secrets-audit-mcp/server.py"]
    }
  }
}

Tools

ToolUse case
scanScan inline text/content
scan_fileScan a single file
scan_directoryScan a directory recursively (skips .git, node_modules, __pycache__, etc.)

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":"."}}}
    EOF

A 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:

LayerToolDetects
Static behaviorsskill-audit-mcpcurl-pipe-sh, exfiltration, prompt injection (68 patterns)
Static secretssecrets-audit-mcpleaked keys/tokens/PEMs (32 rules)

Subscribe — security pulse

Polar.sh — Security Pulse Monthly ships a monthly briefing on new MCP server vulnerabilities, secrets-audit-mcp rule updates, and mitigation playbooks. $5/mo.

Polar.sh — Pro Audit Stack adds 50 paid scan credits + Discord + custom rule submission. $20/mo.


License

MIT. See LICENSE.

Free MCP vs paid x402

This MCP server is free. For server-side / batch / no-install use, the same scanner is a pay-per-call x402 HTTP API: POST https://eltociear-secrets-audit.hf.space/audit ($0.01 USDC on Base) and /audit/url ($0.03). In the official MCP Registry as io.github.eltociear/secrets-audit-mcp.

Professional audit services

Maintained by the same author — paid services on Polar (Stripe checkout):

Full catalog: polar.sh/eltociear

Also live: clean-read ($0.005 / call)

Same operator, same x402 rails: clean-read turns any URL into clean Markdown for AI agents — fetches the page, strips nav/ads/boilerplate (trafilatura), returns the main content with title and word count. POST https://eltociear-skill-audit.hf.space/read — $0.005 USDC on Base, no signup.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.