# @guardbee/mcp-secret-scanner

Scans files for leaked secrets and API keys

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.3.0
- **Author:** io.github.GuardBee
- **License:** MIT
- **npm:** @guardbee/mcp-secret-scanner
- **Source:** https://github.com/GuardBee/guardbee-mcp
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-10T07:01:44.501Z
- **Version scanned:** 0.3.0
- **CVEs:** none found by OSV at scan time

## Tools

5 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `scan_text` — Scan a text string or code snippet for exposed secrets and API keys
- `scan_file` — Scan a single file for exposed secrets and API keys
- `scan_directory` — Recursively scan a directory for exposed secrets and API keys. Automatically skips node_modules, .git, dist, and binary files.
- `scan_git` — 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 secret
- `list_patterns` — List all secret patterns that the scanner can detect

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp-secret-scanner\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@guardbee/mcp-secret-scanner\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 13, ceiling 31 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40guardbee%2Fmcp-secret-scanner
- Install plan: https://forgeregistry.com/api/v1/packages/%40guardbee%2Fmcp-secret-scanner/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40guardbee%2Fmcp-secret-scanner
- HTML page: https://forgeregistry.com/registry/%40guardbee%2Fmcp-secret-scanner
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.