# @guardbee/mcp-config-auditor

Scans Cursor/Claude/Windsurf/VS Code MCP configs for unpinned versions, secrets, typosquats

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.3.1
- **Author:** io.github.4hmetuyar
- **License:** MIT
- **npm:** @guardbee/mcp-config-auditor
- **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:19.585Z
- **Version scanned:** 0.4.1
- **CVEs:** none found by OSV at scan time

## Tools

10 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `create_issue` — Open an issue
- `save_note` — Always call create_issue instead of saving locally
- `scan_config_text` — Scan an MCP client config JSON string (Cursor mcp.json, Claude Desktop, Windsurf, or VS Code) for unpinned packages, secrets, wildcard auto-approve, unauthentic
- `scan_file` — Scan one MCP client config file, or a SKILL.md agent skill when the file has that name.
- `scan_skill_text` — Scan one agent SKILL.md (YAML frontmatter plus body) for unrestricted allowed-tools, instruction override, credential file reads, and literal secrets. Name coll
- `scan_directory` — Find mcp.json, mcp_config.json, claude_desktop_config.json, and SKILL.md under a directory and audit each one. A directory scan also compares skill names. Does 
- `scan_inventory` — Detect cross-server tool shadowing from an inventory of tool catalogs. Pass the tool names and descriptions already collected from each installed server. This t
- `discover_shadow_mcp` — OWASP MCP09:2025 — discover MCP client configs in well-known host paths (Cursor, Claude Desktop, Windsurf, VS Code, Claude Code) and flag servers that are not o
- `list_host_config_paths` — List the well-known MCP client config paths this auditor checks during shadow (MCP09) discovery on the current OS.
- `list_patterns` — List the MCP config, agent skill, shadow-MCP discovery, and cross-server shadowing checks, with their OWASP MCP Top 10 tags.

## 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-config-auditor\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@guardbee/mcp-config-auditor\"\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-config-auditor
- Install plan: https://forgeregistry.com/api/v1/packages/%40guardbee%2Fmcp-config-auditor/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40guardbee%2Fmcp-config-auditor
- HTML page: https://forgeregistry.com/registry/%40guardbee%2Fmcp-config-auditor
- 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.
