@guardbee/mcp-audit-gap-auditor
🇬🇧 English | 🇹🇷 Türkçe | 🇨🇳 中文 | 🇯🇵 日本語 | 🇰🇷 한국어 | 🇧🇷 Português | 🇪🇸 Español | 🇩🇪 Deutsch
[npm version]
[npm downloads]
[License: MIT]
An MCP server that audits MCP server source for OWASP MCP08:2025 — Lack of Audit and Telemetry.
security-proxy already writes a hash-chained audit log at the gateway. This package asks a different question: does the MCP server itself leave a usable, non-leaky trail when a tool runs?
Telemetry is off by default. With GUARDBEE_TELEMETRY=1 it sends the server, tool, success, duration and short parameter values such as a file path; longer strings and fields like content, token or password are replaced with a placeholder. See @guardbee/mcp-telemetry.
What it flags
Logging checks only run in files that look like MCP tool servers, so ordinary console.log(args) helpers elsewhere are ignored.
Quick start
Tools
guardbee.yml:
Feedback
Questions, ideas, or a false positive? Start a thread in GitHub Discussions or open an issue. If GuardBee is useful to you, a ⭐ on the repository helps others find it.