io.github.GuardBee/prompt-leak-scanner
NPM · @GUARDBEE/MCP-PROMPT-LEAK-SCANNER
Catches leaked credentials and PII in outbound LLM prompts
Available components
Last scanned (1 day ago)
Scores higher than 30% 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
- 31 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- 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 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Stability & Change Management0
- Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Tool Coverage0
- Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Tool Safety0
- Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Capabilities0
- Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
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.
- 16 Oct 26 0
- Package version: 0.1.22 → 0.1.23 functional
- 15 Oct 26 0
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- Package version: 0.1.20 → 0.1.22 functional
- 14 Oct 26 0
- Known CVEs: pass → unverified ▼ security
- Known CVEs: pass → partial ▼ security
- Dependency health: 0.85 → unverified ▼ functional
- Dependency health: 0.85 → partial functional
- Package version: 0.1.17 → 0.1.20 functional
- Package version: 0.1.17 → 0.1.19 functional
- Package version: 0.1.17 → 0.1.18 functional
- 13 Oct 26 0
- Package version: 0.1.16 → 0.1.17 functional
- 12 Oct 26 0
- Package version: 0.1.15 → 0.1.16 functional
- 11 Oct 26 49
First indexed and scored.
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 16 Oct 2026 · Analysed npm/@guardbee/mcp-prompt-leak-scanner@0.1.23
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 | 3275040516 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:245095292b32d168ecee6da186270051da2438e11a280df483f517e796371414486a5721c69c84082ed85cee3be47253ead0e091cf687a01ea11c73f1 |
Background: How many MCP packages publish verified provenance →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 31 |
| 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 ~23
List every credential/PII pattern this scanner detects, grouped by category
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scan_directory ~98
Recursively scan a directory of prompt logs or request-body fixtures for leaked credentials and PII
| Name | Type | Req | Description |
|---|---|---|---|
| exclude | array | – | Skip files/dirs whose path contains one of these strings |
| include | array | – | Only scan files whose path contains one of these strings |
| 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 ~52
Scan a single file — plain text, or a JSON chat-request-body fixture (auto-detected) — for leaked credentials and PII
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute or relative path to the file to scan |
No output schema declared.
No examples provided.
scan_messages ~87
Scan an OpenAI/Anthropic-style chat request body (a JSON object with a `messages` array and/or a `system` field) for leaked credentials and PII in every message's text content, before it would be sent to the model.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | The chat request body object, e.g. { model, system, messages: [{ role, content }] } |
No output schema declared.
No examples provided.
scan_text ~95
Scan a raw text string (e.g. a prompt you're about to send to an LLM) for leaked credentials (API keys, private keys, JWTs) and PII (TC Kimlik No, credit card, IBAN, email, phone) — checksum-validated where applicable to keep false positives low.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The text to scan |
| label | string | – | Optional label shown in findings |
No output schema declared.
No examples provided.
How do I install the io.github.GuardBee/prompt-leak-scanner MCP server?
io.github.GuardBee/prompt-leak-scanner runs locally as an npm package, launched with npx -y @guardbee/mcp-prompt-leak-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-prompt-leak-scanner
claude mcp add guardbee-prompt-leak-scanner -- npx -y @guardbee/mcp-prompt-leak-scanner
What is the io.github.GuardBee/prompt-leak-scanner MCP server?
io.github.GuardBee/prompt-leak-scanner is an MCP server listed in the public MCP registry as io.github.GuardBee/prompt-leak-scanner. Catches leaked credentials and PII in outbound LLM prompts. This page covers its npm package (@guardbee/mcp-prompt-leak-scanner).
Is the io.github.GuardBee/prompt-leak-scanner MCP server safe to use?
io.github.GuardBee/prompt-leak-scanner scores 49 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 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/prompt-leak-scanner MCP server expose?
io.github.GuardBee/prompt-leak-scanner exposes 5 tools: scan_text, scan_messages, scan_file, scan_directory, list_patterns. Their descriptions and schemas cost roughly 355 tokens of context every time the server is loaded.
Is the io.github.GuardBee/prompt-leak-scanner MCP server still maintained?
io.github.GuardBee/prompt-leak-scanner is still listed as active in the MCP registry. We last reached this channel on 16 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/prompt-leak-scanner MCP server under?
io.github.GuardBee/prompt-leak-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.