New:Introducing Socket Scanning for VS Code Marketplace Extensions.Learn more →
Get Started

@guardbee/mcp-audit-gap-auditor

Package Overview
Dependencies
Maintainers
1
Versions
6
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@guardbee/mcp-audit-gap-auditor

MCP server that audits MCP server source for OWASP MCP08:2025 (Lack of Audit and Telemetry) — missing tool-call logging, raw args/results in logs, disabled audit sinks, and tool errors swallowed without a record

latest
Source
npmnpm
Version
0.3.0
Version published
Weekly downloads
0
Maintainers
1
Weekly downloads
 
Created
Source

@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.

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

PatternSeverityOWASPMeaning
mcp_server_without_tool_audithighMCP08:2025McpServer / FastMCP registers tools but the file never mentions audit/telemetry
raw_tool_args_loggedcriticalMCP08:2025console/logger logs the full args/params/input object
raw_tool_result_loggedhighMCP08:2025Full result / toolResult logged
audit_disabled_in_codehighMCP08:2025audit: false, enableAudit: false, GUARDBEE_TELEMETRY=0, …
tool_error_swallowed_silentlymediumMCP08:2025Empty / return-only catch around a tool handler
audit_log_without_correlation_idmediumMCP08:2025audit.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

ToolPurpose
scan_textScan a source string
scan_fileScan one file
scan_directoryRecursive scan
list_patternsList 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.

Keywords

mcp

FAQs

Package last updated on 22 Oct 2026

Related posts