Secrets-LE
NPM · SECRETS-LE-MCP · SCANNED SEP 21
Detect hardcoded secrets in source and config. Reports masked previews, never the values.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 37 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 189 tokens (~189/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Secrets-LE MCP server?
Secrets-LE runs locally as an npm package, launched with npx -y secrets-le-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · secrets-le-mcp
claude mcp add nolindnaidoo-secrets-le -- npx -y secrets-le-mcp
{
"mcpServers": {
"nolindnaidoo-secrets-le": {
"command": "npx",
"args": [
"-y",
"secrets-le-mcp"
]
}
}
} {
"servers": {
"nolindnaidoo-secrets-le": {
"command": "npx",
"args": [
"-y",
"secrets-le-mcp"
]
}
}
} codex mcp add nolindnaidoo-secrets-le -- npx -y secrets-le-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nolindnaidoo-secrets-le": {
"type": "local",
"command": [
"npx",
"-y",
"secrets-le-mcp"
],
"enabled": true
}
}
} openclaw mcp add nolindnaidoo-secrets-le --command npx --arg -y --arg secrets-le-mcp
mcp_servers:
nolindnaidoo-secrets-le:
command: "npx"
args: ["-y", "secrets-le-mcp"] {
"McpServers": {
"nolindnaidoo-secrets-le": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"secrets-le-mcp"
]
}
}
} assistant mcp add nolindnaidoo-secrets-le -t stdio -c npx -a -y secrets-le-mcp
{
"mcpServers": {
"nolindnaidoo-secrets-le": {
"command": "npx",
"args": [
"-y",
"secrets-le-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 0
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
- Package version: 2.2.4 → 2.3.0 functional
- 16 Sept 26 0
- Package version: 2.2.4 → 2.3.0 functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 −3
- Stability: pass → 0.77 functional
- 13 Sept 26 0
- Stability: 0.97 → pass security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed npm/secrets-le-mcp@2.3.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
detect_secrets ~189
Detect hardcoded secrets — API keys, passwords, tokens and private keys — in source or configuration text. Reports each finding by type, confidence, key name and 1-based position. Values are never returned: previews are truncated and length-annotated, and the surrounding context line has the secret masked out, so a finding can be located without the credential leaving the machine it was found on.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The text to scan. |
| includeApiKeys | boolean | – | Include API key detectors. |
| includePasswords | boolean | – | Include password detectors. |
| includePrivateKeys | boolean | – | Include private key detectors. |
| includeTokens | boolean | – | Include token detectors. |
| maxResults | integer | – | Cap on returned findings (default 500). meta.truncated reports whether any were dropped. |
| sensitivity | string | – | Detection threshold. Higher sensitivity reports more low-confidence matches. |
No output schema declared.
No examples provided.
What is the Secrets-LE MCP server?
Secrets-LE is an MCP server listed in the public MCP registry as io.github.nolindnaidoo/secrets-le. Detect hardcoded secrets in source and config. Reports masked previews, never the values. This page covers its npm package (secrets-le-mcp).
Is the Secrets-LE MCP server safe to use?
Secrets-LE scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Secrets-LE MCP server expose?
Secrets-LE exposes 1 tool: detect_secrets. Their descriptions and schemas cost roughly 189 tokens of context every time the server is loaded.
Is the Secrets-LE MCP server still maintained?
Secrets-LE is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Secrets-LE MCP server under?
Secrets-LE declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.