Detect hardcoded secrets in source and config. Reports masked previews, never the values.
MCPpedia last refreshed this data
io.github.nolindnaidoo/secrets-le is an MCP server that detect hardcoded secrets in source and config. Reports masked previews, never the values. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 89/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"secrets-le": {
"args": [
"-y",
"secrets-le-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Useful? A star or rating is how other developers find it — > ★ GitHub · > ★ Open VSX · > ★ Marketplace
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'secrets-le-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked secrets-le-mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
Transport for TMCP using STDIO
The graph based agentic IDE
Buddhist canon tools: search, passages, cross-canon parallels, dictionaries — all URN-cited.
MCP Security Weekly
Get CVE alerts and security updates for io.github.nolindnaidoo/secrets-le and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Find hardcoded credentials across your workspace, then redact them in place
API keys, tokens, passwords, private keys — 100% local, nothing leaves your machine
Useful? A star or rating is how other developers find it — ★ GitHub · ★ Open VSX · ★ Marketplace
Open a workspace, press Ctrl+Alt+S (Cmd+Alt+S on Mac), and every detected secret lands in a results document — grouped by file, with line/column positions pointing at the value itself. Run Secrets-LE: Sanitize Secrets to replace the secrets in the active file with a placeholder. Works in VS Code and in VS Code–based editors like Cursor and VSCodium (installable from Open VSX).
Detection is regex-based over the full text of each file, so it works on any text format — code, configs, .env files, YAML, JSON, logs. It is a pre-commit safety net, not a guarantee: a scanner built on patterns can miss secrets and can flag non-secrets. Review the results.
| Where | What you get | Install |
|---|---|---|
| VS Code | Detection and in-place sanitising, in your editor | Marketplace |
| Cursor, VSCodium, Windsurf | The same extension | Open VSX |
| A terminal or a CI step | The same run over a whole tree, with exit codes | cargo install secrets-le · crates.io |
| Any MCP agent, via Node | detect_secrets over stdio | npx secrets-le-mcp · npm |
| Zed | The MCP server as a context server | add it by hand (no listing yet) |
The same engine runs as an MCP server, so an agent can call it directly instead of you running a command.
| Editor | How |
|---|---|
| VS Code 1.101+ | Nothing to install — the extension registers detect_secrets with agent mode |
| Zed | No listing yet — add the MCP server by hand |
| Claude Code | claude mcp add secrets-le -- npx -y secrets-le-mcp |
| Cursor, Windsurf, anything else | point it at npx secrets-le-mcp |
detect_secrets(content, sensitivity?, includeApiKeys?, includePasswords
... [View full README on GitHub](https://github.com/nolindnaidoo/secrets-le#readme)