Agent Trace Auditor
Audit agent execution traces through MCP so you can inspect what autonomous coding runs did after you ship agent features.
Overview
io.github.lazymac2x/agent-trace-auditor is a MCP server for the Operate phase that provides a remote Cloudflare Workers endpoint to audit agent execution traces over MCP.
What is this MCP server?
- Cloudflare Workers MCP server with remote streamable-http endpoint for trace auditing
- Public MCP URL: https://api.lazy-mac.com/agent-trace-auditor/mcp
- Complements agent builds that need post-hoc review of tool calls and steps
- Source repository: lazymac2x/agent-trace-auditor-api on GitHub
- MCP server schema 2025-09-29 with packaged version 1.0.0
- MCP server version 1.0.0
- 1 documented streamable-http remote endpoint
- Cloudflare Workers deployment via api.lazy-mac.com
What problem does it solve?
When agents chain tools autonomously, you often cannot see what happened without bespoke logging or dashboard work.
Who is it for?
Solo builders running agent workflows in production who want a quick MCP hook for trace review tied to Lazy Mac infrastructure.
Skip if: Organizations needing certified SIEM integration, full on-device trace storage, or detailed tool documentation in this minimal catalog stub.
What do I get? / Deliverables
Registering the auditor MCP gives your agent a protocol-native path to inspect or process traces instead of parsing raw logs by hand.
- Connected MCP remote for agent trace auditing
- Ability to invoke auditor tools from the agent client once registered
- Documented v1.0.0 server identity for Skillselion catalog linking
Recommended MCP Servers
Journey fit
Trace auditing matters most once agents run real workflows in production, which maps to Operate even though you may first connect the MCP during Build. monitoring is the canonical shelf because the server name and purpose center on reviewing agent traces for visibility and accountability, not on writing application code.
How it compares
MCP trace-audit integration, not a static code-review skill or local test runner.
Common Questions / FAQ
Who is io.github.lazymac2x/agent-trace-auditor for?
Builders operating agent-powered products who need MCP-accessible trace auditing without standing up a custom observability service first.
When should I use io.github.lazymac2x/agent-trace-auditor?
Use it in Operate when you are monitoring agent runs and want the agent or ops workflows to pull audits via MCP after shipping integrations.
How do I add io.github.lazymac2x/agent-trace-auditor to my agent?
Configure the remote MCP server URL https://api.lazy-mac.com/agent-trace-auditor/mcp (streamable-http) in your agent client and confirm tools against agent-trace-auditor-api.