The Model Context Protocol gave AI agents a clean way to reach into systems. In a year it has become the default tool surface for serious agents. That is mostly good news. The mostly is the operative word. Without care, MCP servers fragment the audit story. Tool calls land in three places: in the agent's runtime, in the gateway, and in the MCP server's own logs. None of them line up. By the time a regulator asks what happened, you have three formats and zero answers. This post walks how I wire MCP into Akmon. The result is a single audit chain that captures every MCP tool call as a ToolCall event, with deterministic linkage in the journal, and a reviewable AGEF bundle at the end. The commands and flags here are real Akmon v2.0.0 surface. I will note where Phase 4 features apply. Why MCP audit logging is harder than it looks Three reasons. First, MCP is a fan out. A single agent session can call three MCP servers, each with its own tools, its own version, and its own logging story.…