Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
Rumblingb avatar

Agent Audit Mcp

  • 2 repo stars
  • Updated July 13, 2026
  • Rumblingb/agent-audit-mcp

Agent Audit MCP is a MCP server that keeps an immutable audit trail of agent-to-agent interactions.

About

Agent Audit MCP provides an immutable audit trail for agent-to-agent interactions, aimed at developers running orchestrated or multi-agent setups through MCP. When one agent delegates to another, you get a durable record instead of ephemeral chat logs—useful for Operate monitoring, Ship security reviews, and Grow support when users question automated decisions. The registry lists v1.0.0 from Rumblingb’s GitHub repo with a concise security-observability positioning. founders often skip formal audit until something breaks; this server is for the point where multiple agents, cron-driven workers, or handoff chains need forensic clarity. Setup is typically intermediate: register the MCP server, wire your orchestration layer to emit or query audit events per project README. It is observability infrastructure, not a skill that plans features or writes code. Pair mentally with budget/wallet controls when spend and action both need governance.

  • Immutable audit trail focused on agent-to-agent interactions
  • Suited for multi-agent orchestration and delegated sub-agents
  • v1.0.0 MCP server from Rumblingb/agent-audit-mcp on GitHub
  • Complements wallet/budget MCP from the same publisher for full agent ops
  • Registry-first description without extra tool surface listed in snippet

Agent Audit Mcp by the numbers

  • Data as of Jul 14, 2026 (Skillselion catalog sync)
claude mcp add AgentAuditMcp -- npx -y Rumblingb/agent-audit-mcp

Add your badge

Show developers this MCP server is listed on Skillselion. Paste this into your README.

Listed on Skillselion
repo stars2
Last updatedJuly 13, 2026
RepositoryRumblingb/agent-audit-mcp

What it does

Attach an immutable audit trail to multi-agent MCP workflows so developers can debug and defend agent-to-agent actions.

Who is it for?

Best when you're running chained or peer agents via MCP and need tamper-evident interaction history without building a custom logging service.

Skip if: Single-agent coding sessions with no delegation, or teams that already centralize logs in a full APM with MCP-unaware ingestion only.

What you get

After registration, agent-to-agent events can be recorded immutably so you can monitor, investigate, and support users with a clear timeline.

  • Immutable agent-to-agent interaction audit path
  • Investigation-ready timeline for support and incidents
  • v1.0.0 registered MCP audit endpoint

By the numbers

  • Registry version 1.0.0
  • GitHub repository id 1235193121 in server metadata
  • Single server entry described as immutable audit trail
README.md

AgentPay

AgentAudit MCP

Your agent now has an immutable, tamper-evident log of every action it takes — each event cryptographically linked to the previous one so any modification breaks the chain and is immediately detectable.

What your agent can do

  • Log any of 16 event types (payments, tasks, disputes, identity checks, messages) with a SHA-256 hash that includes the previous event's hash
  • Retrieve the full history of any agent by ID — every action, in order, with timestamps
  • Search across the audit trail by agent, event type, severity level, or date range
  • Verify chain integrity between any two events and get a per-event pass/fail breakdown showing exactly which link was tampered
  • Track five severity levels — info, notice, warning, error, critical — for compliance triage
  • Get statistics across the entire audit trail: events by type, by severity, and most active agents

Installation

Requires: Python 3.10+, mcp and fastmcp packages.

pip install mcp fastmcp

Claude Desktop — add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "agent-audit": {
      "command": "python",
      "args": ["/absolute/path/to/agent-audit-mcp/server.py"]
    }
  }
}

Cursor — add to .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "agent-audit": {
      "command": "python",
      "args": ["/absolute/path/to/agent-audit-mcp/server.py"]
    }
  }
}

Data is stored locally at ~/.agentaudit/chain.json. No data leaves your machine.

Tool Reference

Tool Description Key params
audit_log Log an event and append it to the hash chain event_type (one of 16), agent_id, severity, details_json
audit_get_event Retrieve full event details by ID event_id
audit_search Filter events by agent, type, severity, or date range agent_id, event_type, severity, from_date, to_date, max_results
audit_get_agent_history All events for one agent, newest first agent_id, max_events
audit_verify_chain Check SHA-256 chain integrity between two events; returns per-event PASS/FAIL from_event_id, to_event_id
audit_stats Summary: total events, breakdown by type/severity, top 5 active agents

Supported event types: task_created, task_assigned, task_completed, task_failed, payment_sent, payment_received, payment_refunded, dispute_raised, dispute_resolved, identity_verified, capability_used, agent_registered, agent_rated, agent_offline, message_sent, message_received

Security

Audit data is written atomically (write-to-temp, then os.replace) to prevent partial writes from corrupting the chain. The hash covers every field including the previous event's hash — you cannot insert, delete, or modify any event without breaking all subsequent hashes. audit_verify_chain recomputes each hash from scratch rather than trusting stored values.

All data is stored locally. No network requests are made by this server.

Pricing

Plan Price Included
Pro $19/month Unlimited audit events, full chain verification

Subscribe via Stripe

License

Proprietary — see subscription terms. Source: github.com/Rumblingb/agent-audit-mcp

Recommended MCP Servers

How it compares

Agent interaction audit MCP, not a finance wallet or MCP firewall product.

FAQ

Who is Agent Audit MCP for?

Developers and small teams orchestrating multiple AI agents who need immutable records of handoffs and peer calls.

When should I use Agent Audit MCP?

Use it once agents call other agents in production—or before launch if auditors or partners require proof of automated delegation paths.

How do I add Agent Audit MCP to my agent?

Add io.github.Rumblingb/agent-audit-mcp from the MCP registry to your client configuration and connect your orchestration code to the server per the GitHub repository instructions.

Monitoringmonitoringsupport

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.