About audit-gap-auditor
An MCP server for checking MCP server source code for OWASP MCP08 audit and telemetry gaps. It helps developers identify missing invocation records, unsafe logging, disabled audits, and silently swallowed errors.
Key features
- 01Scan source text, files, and directories
- 02Detect missing tool-call audit records
- 03Flag raw tool arguments or results in logs
- 04Find disabled auditing and silent tool failures
- 05Report findings in SARIF format
Use cases
- 01Review an MCP server before release
- 02Find sensitive arguments written to logs
- 03Check whether tool errors disappear silently
MCP support
Provides MCP tools to scan source text, files, and directories and list MCP08 audit checks.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
4Saved tool list · updated 1w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| label | string | No | Optional label shown in findings (e.g. filename) |
| content | string | Yes | The code content to scan |
Details
From the project README@guardbee/mcp-audit-gap-auditor
🇬🇧 English | 🇹🇷 Türkçe | 🇨🇳 中文 | 🇯🇵 日本語 | 🇰🇷 한국어 | 🇧🇷 Português | 🇪🇸 Español | 🇩🇪 Deutsch
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=1it sends the server, tool, success, duration and short parameter values such as a file path; longer strings and fields likecontent,tokenorpasswordare replaced with a placeholder. See@guardbee/mcp-telemetry.
Claude ──► audit-gap-auditor ──► MCP server source
│
├─ missing-telemetry (tools registered, no audit/log/telemetry of invocations)
├─ unsafe-logging (raw tool args or results written to logs)
├─ disabled-audit (audit/telemetry hard-disabled in source)
└─ silent-failure (tool errors swallowed with an empty catch)
What it flags
| Pattern | Severity | OWASP | Meaning |
|---|---|---|---|
mcp_server_without_tool_audit | high | MCP08:2025 | McpServer / FastMCP registers tools but the file never mentions audit/telemetry |
raw_tool_args_logged | critical | MCP08:2025 | console/logger logs the full args/params/input object |
raw_tool_result_logged | high | MCP08:2025 | Full result / toolResult logged |
audit_disabled_in_code | high | MCP08:2025 | audit: false, enableAudit: false, GUARDBEE_TELEMETRY=0, … |
tool_error_swallowed_silently | medium | MCP08:2025 | Empty / return-only catch around a tool handler |
audit_log_without_correlation_id | medium | MCP08:2025 | audit.log({…}) with no sessionId / requestId / similar |
Logging checks only run in files that look like MCP tool servers, so ordinary console.log(args) helpers elsewhere are ignored.
Quick start
{
"mcpServers": {
"guardbee-audit-gap-auditor": {
"command": "npx",
"args": ["-y", "@guardbee/mcp-audit-gap-auditor"]
}
}
}
npx @guardbee/mcp-audit-gap-auditor scan ./src --fail-on=high --format=sarif > results.sarif
Tools
| Tool | Purpose |
|---|---|
scan_text | Scan a source string |
scan_file | Scan one file |
scan_directory | Recursive scan |
list_patterns | List MCP08 checks |
guardbee.yml:
audit-gap-auditor:
fail-on: high
max-files: 5000
exclude:
- "fixtures/"
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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.