# @guardbee/mcp-ai-code-scanner

Scans code for insecure LLM/AI integration: exposed keys, unsafe output, prompt injection

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.3.2
- **Author:** io.github.4hmetuyar
- **License:** MIT
- **npm:** @guardbee/mcp-ai-code-scanner
- **Source:** https://github.com/GuardBee/guardbee-mcp
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- 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-10T22:28:26.682Z
- **Version scanned:** 0.3.2
- **CVEs:** none found by OSV at scan time

## Tools

7 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `execute_command`
- `run_shell` — ...
- `get_weather` — Returns weather
- `scan_text` — Scan a text string or code snippet for insecure AI/LLM integration patterns (client-exposed keys, unsafe output handling, excessive agent tool permissions, PII 
- `scan_file` — Scan a single file for insecure AI/LLM integration patterns
- `scan_directory` — Recursively scan a directory for insecure AI/LLM integration patterns. Automatically skips node_modules, .git, dist, and binary files.
- `list_patterns` — List all AI/LLM security patterns that the scanner can detect, grouped by category (including any custom rules loaded from .guardbee/rules)

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp-ai-code-scanner\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@guardbee/mcp-ai-code-scanner\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Extensive to critical — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs commands; runs on your machine.
- Floor 45, ceiling 73 (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-ai-code-scanner
- Install plan: https://forgeregistry.com/api/v1/packages/%40guardbee%2Fmcp-ai-code-scanner/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40guardbee%2Fmcp-ai-code-scanner
- HTML page: https://forgeregistry.com/registry/%40guardbee%2Fmcp-ai-code-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.