mcp-audit-gateway logo

mcp-audit-gateway

Free

Tamper-proof audit trail for AI Agent tool calls. Cryptographically signed, hash-chained records that prove what your agents did

Visit Website
Related by shared tags and keywordsfontaineloopgatemaintainer-agent
ai-agentai-agentsai-safetyattestationaudit-logsaiai assistantautomation

Overview

mcp-audit-gateway is a tamper-evident audit trail for AI agent tool calls. It can wrap an MCP server so that every tool call is cryptographically signed and hash-chained while the MCP server continues to work as before. The project provides a CLI for wrapping, tailing, verifying, serving, and key generation.

The wrap command spawns the MCP server as a child process and sits between the client and server on stdio. It forwards all messages transparently, signing and logging only tools/call responses. On first run, a signing key is auto-generated in ~/.mcp-audit/key.hex, and no configuration is needed. Audit records include fields such as id, timestamp, method, toolName, args, durationMs, success, previousHash, and attestation.

A full gateway mode is available for teams that also need access control, rate limiting, and multi-server routing. It adds a policy engine with glob-based ACLs and per-principal rate limits, tool namespacing across multiple upstream MCP servers, OpenTelemetry traces and metrics export, upstream health management with automatic reconnection, and Ed25519 signatures. The project also includes cross-SDK differential testing: MCP has 10 official SDKs and no cross-SDK conformance testing, and the harness runs 40 serialization edge-case tests across all 10 SDKs, reporting 26 wire-level divergences across 8 distinct serializers.

Pricing

Free

Detailed plans have not been confirmed in our catalog. Check the official website for current limits and billing terms.

Visit Website

Prices and limits may change. Confirm the currency, billing period, seat minimum and usage caps on the official website.

Use Cases

  • Teams use mcp-audit wrap to add signed, hash-chained logging to an existing MCP server without changing server behavior.
  • Teams use mcp-audit tail to live stream tool calls.
  • Teams use mcp-audit verify to verify chain integrity of an audit log.
  • Teams use full gateway mode to enforce access control, rate limiting, and multi-server routing.
  • Teams use the cross-SDK differential harness in CI to catch serialization regressions in their own MCP server or client.
  • Teams use Docker to run the cross-SDK differential test self-contained without host dependencies.
  • Teams use Python verification to check cross-language parity of the audit chain.
  • Teams use mcp-audit keygen to generate an Ed25519 key pair.

Features

Record AI agent tool calls

Sign entries with HMAC-SHA256

Chain each entry to its predecessor

Verify whether records were altered

Detect missing entries through broken chains

Reviews

No reviews yet. Be the first to share your experience!