io.github.GuardBee/secret-scanner
NPM · @GUARDBEE/MCP-SECRET-SCANNER
Scans files for leaked secrets and API keys
Available components
Last scanned (12 hours ago)
Scores higher than 85% of npm servers
Category Security
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 Security98
- 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
- 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to GuardBee/guardbee-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 566 tokens (~94/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 23 Oct 26 +46
- Injection markers: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Dependency health: unverified → 0.86 ▲ functional
- Stability: unverified → 0.27 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 22 Oct 26 −33
- Stability: 0.20 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Known CVEs: unverified → partial ▲ security
- Known CVEs: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- Dependency health: unverified → 0.85 ▲ functional
- Security disclosure: fail → pass ▲ functional
- Package version: 0.6.11 → 1.0.2 functional
- Package version: 0.6.11 → 1.0.1 functional
- Package version: 0.6.11 → 1.0.0 functional
- 21 Oct 26 0
- Package version: 0.6.10 → 0.6.11 functional
- 20 Oct 26 −10
- Known CVEs: pass → unverified ▼ security
- Dependency health: 0.85 → unverified ▼ functional
- Package version: 0.6.8 → 0.6.10 functional
- Package version: 0.6.8 → 0.6.9 functional
- 19 Oct 26 0
- Package version: 0.6.7 → 0.6.8 functional
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +43
- Injection markers: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.07 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Dependency health: unverified → 0.85 ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 16 Oct 26 −11
- Known CVEs: pass → unverified ▼ security
- Dependency health: 0.85 → unverified ▼ functional
- Package version: 0.6.6 → 0.6.7 functional
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 25 Oct 2026 · Analysed npm/@guardbee/mcp-secret-scanner@1.0.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | GuardBee/guardbee-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/GuardBee/guardbee-mcp/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 3386363608 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b715d627bab1c285244d3d7b2f9a26c5e6fa3b85daa674f2d592c048772baf7de28b5487a66d80ca9f36260baa241c713b9f1d990c7e844bd9bc632a8 |
Background: How many MCP packages publish verified provenance →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 30 |
| 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 →
list_patterns ~18
List all secret patterns that the scanner can detect
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scan_agent_history ~98
Scan the transcripts coding agents keep on this machine (Claude Code, Codex, Gemini CLI, Continue) for secrets that were pasted into a chat or printed by a command. Such a secret was already sent to the model provider and should be rotated. Each secret is reported once with how often it appears.
| Name | Type | Req | Description |
|---|---|---|---|
| entropy | boolean | – | Also flag random-looking values assigned to secret-like names (default false here: transcripts hold a lot of code) |
No output schema declared.
No examples provided.
scan_directory ~155
Recursively scan a directory for exposed secrets and API keys. Automatically skips node_modules, .git, dist, and binary files.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline | string | – | Path to a baseline file: only findings not in it are reported |
| entropy | boolean | – | Also flag random-looking values assigned to secret-like names (default true) |
| exclude | array | – | Skip files/dirs whose path contains one of these strings |
| include | array | – | Only scan files whose path contains one of these strings (e.g. [".env", ".ts"]) |
| maxFiles | integer | – | Maximum number of files to scan (default: 5000) |
| path | string | yes | Absolute or relative path to the directory to scan |
No output schema declared.
No examples provided.
scan_file ~55
Scan a single file for exposed secrets and API keys
| Name | Type | Req | Description |
|---|---|---|---|
| entropy | boolean | – | Also flag random-looking values assigned to secret-like names (default true) |
| path | string | yes | Absolute or relative path to the file to scan |
No output schema declared.
No examples provided.
scan_git ~169
Scan a git repository for secrets in what git says was added: the staged changes (before a commit) or every commit's added lines (history). History finds secrets that were deleted from the files but are still in the repository.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline | string | – | Path to a baseline file: only findings not in it are reported |
| entropy | boolean | – | Also flag random-looking values assigned to secret-like names (default true) |
| maxCommits | integer | – | History only: stop after this many commits |
| mode | string | yes | staged: lines added in the index; history: lines added by each commit |
| path | string | yes | A directory inside the git repository |
| range | string | – | History only: a revision range such as main..HEAD (default: all refs) |
No output schema declared.
No examples provided.
scan_text ~71
Scan a text string or code snippet for exposed secrets and API keys
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The text content to scan |
| entropy | boolean | – | Also flag random-looking values assigned to secret-like names (default true) |
| label | string | – | Optional label shown in findings (e.g. filename) |
No output schema declared.
No examples provided.
How do I install the io.github.GuardBee/secret-scanner MCP server?
io.github.GuardBee/secret-scanner runs locally as an npm package, launched with npx -y @guardbee/mcp-secret-scanner. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @guardbee/mcp-secret-scanner
claude mcp add guardbee-secret-scanner -- npx -y @guardbee/mcp-secret-scanner
What is the io.github.GuardBee/secret-scanner MCP server?
io.github.GuardBee/secret-scanner is an MCP server listed in the public MCP registry as io.github.GuardBee/secret-scanner. Scans files for leaked secrets and API keys. This page covers its npm package (@guardbee/mcp-secret-scanner).
Is the io.github.GuardBee/secret-scanner MCP server safe to use?
io.github.GuardBee/secret-scanner scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.GuardBee/secret-scanner MCP server expose?
io.github.GuardBee/secret-scanner exposes 6 tools: scan_text, scan_file, scan_directory, scan_git, scan_agent_history, list_patterns. Their descriptions and schemas cost roughly 566 tokens of context every time the server is loaded.
Is the io.github.GuardBee/secret-scanner MCP server still maintained?
io.github.GuardBee/secret-scanner is still listed as active in the MCP registry. We last reached this channel on 25 October 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 io.github.GuardBee/secret-scanner MCP server under?
io.github.GuardBee/secret-scanner declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.