Secret Scanner is listed as active in the registry but did not answer our last check. It exposes 1 tools.
Scan configs, files, or text for leaked secrets and obvious misconfigurations. Nothing stored.
Secret Scanner does not always answer
Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.
claude mcp add secret-scanner --transport http https://mcp.knurl.tools/mcphttps://mcp.knurl.tools/mcp[mcp_servers.secret-scanner]
url = "https://mcp.knurl.tools/mcp"{
"mcpServers": {
"secret-scanner": {
"url": "https://mcp.knurl.tools/mcp"
}
}
}{
"servers": {
"secret-scanner": {
"type": "http",
"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_for_secrets
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.knurl.tools/mcp | streamable-http | answering | 8000 ms | 6 min ago |
Alternatives to Secret Scanner
same job, measured the same wayScans files for leaked secrets and API keys
Scans files for leaked secrets and API keys
Scans AI coding sessions and assistant configs for leaked secrets and risky hooks; local, redacted
Check text for leaked credentials before an agent writes or commits it. Runs locally.
Find every leaked secret on your machine — API keys in .env files, shell history, and configs.
Code security scanner for founders and small teams: leaked secrets, missing RLS, injection, CVEs
Scans code changes for leaked secrets and insecure config, with actionable fixes for AI agents.
Offline secret scanning for AI agents. Redacted findings; scans text and files in a chosen root.
Secret Scanner — questions
Answers built from our own checks of this server.