secret-scanner
Scan configs, files, or text for leaked secrets and obvious misconfigurations. Nothing stored.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"secret-scanner": {
"url": "https://mcp.knurl.tools/mcp"
}
}
}Remote endpoints
https://mcp.knurl.tools/mcpstreamable-httpWhat it can do
Tool inventory
Tools (1)
🟢scan_for_secrets(text, files)
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.
Input Schema
{
"type": "object",
"properties": {
"text": {
"type": "string",
"description": "A single blob to scan."
},
"files": {
"type": "array",
"items": {
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "Filename or path (e.g. \".env\")."
},
"content": {
"type": "string",
"description": "Raw text content of the file."
}
},
"required": [
"name",
"content"
],
"additionalProperties": false
},
"description": "Multiple named files to scan."
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}Community
Evidence