mcpbeat Sign in

Secret Scanner MCP Server

answering

Secret Scanner is answering right now. Last checked 14 min ago. It exposes 1 tools.

Scan configs, files, or text for leaked secrets and obvious misconfigurations. Nothing stored.

Uptime history 48 days of history
48 days agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
436 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Secret Scanner every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add secret-scanner --transport http https://mcp.knurl.tools/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "secret-scanner": {
      "url": "https://mcp.knurl.tools/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.secret-scanner]
url = "https://mcp.knurl.tools/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "secret-scanner": {
      "url": "https://mcp.knurl.tools/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "secret-scanner": {
      "url": "https://mcp.knurl.tools/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

scan
scan_for_secrets
Scan a pasted config, file, code snippet, or blob for exposed credentials and obvious security misconfigurations. Use whenever a user shares a .env, docker-compose.yml, nginx.conf, JSON/YAML config, or any text and asks "is this safe to share/commit?", "any leaked API keys/secrets?", or "what's misconfigured?". Detects cloud credentials, Stripe/GitHub/GitLab tokens, OpenAI/Anthropic/Gemini/Hugging Face/Groq/Replicate keys, private-key blocks, JWTs, DB connection strings, plus misconfigs like debug-on, 0.0.0.0 binds, disabled TLS verification, privileged containers, and weak passwords. Deterministic. It analyzes the provided text and returns findings only — it never stores, transmits, or requires any live credential.

Endpoints

URLTransportStateLatencyChecked
https://mcp.knurl.tools/mcp streamable-http answering 482 ms 14 min ago

Alternatives to Secret Scanner

same job, measured the same way
Skarn
by getskarn

Scans AI coding sessions and assistant configs for leaked secrets and risky hooks; local, redacted

709 installs/wk local only
Secret Scan
by agentic-income-bot

Check text for leaked credentials before an agent writes or commits it. Runs locally.

local only
Ghosthunt
by 78degrees

Find every leaked secret on your machine — API keys in .env files, shell history, and configs.

55 installs/wk local only
LeakRank Guard
by prototeemo

Scans code changes for leaked secrets and insecure config, with actionable fixes for AI agents.

56 installs/wk local only
Env Secret Exposure Analyzer MCP
by vola-trebla

Scans projects for secret exposure: leaked API keys, unprotected .env files, and secrets in logs.

36 installs/wk local only
Husk
by husk-security

Local-first defensive scanner for vulnerable dependencies, leaked secrets, and risky agent configs

233 installs/wk local only
Vibescan MCP Server
by aguantar

MCP server for VibeScan — scan projects for leaked secrets and security issues

68 installs/wk local only
D
Flare
by flarehq

Scan a running app or repo for leaked secrets, exposed routes and open RLS, and verify live keys

83 installs/wk local only

Secret Scanner — questions

Answers built from our own checks of this server.

What can Secret Scanner do?
It exposes 1 tools, read directly from the server on our last check. Among them: scan_for_secrets. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Secret Scanner working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 436 ms. The bar chart above shows every period we have measured.
How do I connect Secret Scanner?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Secret Scanner need an API key?
No. Secret Scanner completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Secret Scanner?
It answers our handshake in 436 ms on average, which is faster than 34% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.