Skip to main content
Glama
nyx-builds

mcp-audit

by nyx-builds

mcp-audit


mcp-audit is a Model Context Protocol server that gives AI agents observability over their own tool calls. Every time your agent invokes a tool — whether it's an MCP tool, a custom function, or an external API — mcp-audit records who called what, when, how long it took, what it cost, and whether it succeeded.

Why?

AI agents are increasingly autonomous, calling dozens of tools per session. But agents are blind to their own behavior:

  • ❌ No way to see which tools an agent called or how often

  • ❌ No cost tracking — agents can silently rack up API bills

  • ❌ No latency visibility — one slow tool tanks the whole session

  • ❌ No error correlation — which tool is failing 30% of the time?

  • ❌ No alerting — you find out about runaway costs after the fact

mcp-audit fixes this. It's an MCP server that agents use to audit themselves.

Related MCP server: production-grade-mcp-agentic-system

Features

  • 📊 Call Recording — log every tool invocation with timing, cost, tokens, and result

  • 🔍 Flexible Querying — filter by session, agent, tool, server, status, cost, tags

  • 📈 Aggregate Analytics — error rate, p50/p95/p99 latency, total cost, top tools

  • 💰 Cost Breakdown — see exactly which tools are consuming budget, grouped by tool/server/session

  • 🚨 Alert Rules — set thresholds (e.g. "alert if error_rate > 50%" or "alert if total_cost > $10")

  • 📝 Trace Events — fine-grained structured logging within calls (sub-steps, HTTP requests, DB queries)

  • 🏷️ Agent Reports — comprehensive per-agent performance summaries

  • 🪝 Context Manager — Python with block for automatic call tracing

Quick Start

Install

pip install mcp-audit

Use as a Python library

from mcp_audit import AuditEngine, traced_call

engine = AuditEngine()
session = engine.start_session(agent_id="my-agent")

# Wrap any function call with automatic tracing
with traced_call(engine, session_id=session.id, tool_name="web_search") as tc:
    tc.set_cost(0.003)
    tc.set_tokens(input_tokens=500, output_tokens=200)
    result = search("best MCP servers")
    tc.set_result(result)

# Query analytics
stats = engine.get_stats(session_id=session.id)
print(f"Total cost: ${stats['total_cost_usd']}")
print(f"P95 latency: {stats['p95_latency_ms']}ms")
print(f"Error rate: {stats['error_rate']}%")

Use as an MCP server

Add to your MCP client config (Claude Desktop, Cursor, etc.):

{
  "mcpServers": {
    "mcp-audit": {
      "command": "mcp-audit",
      "args": ["serve"]
    }
  }
}

Your agent can now call audit tools like record_call, get_stats, create_alert_rule, and evaluate_alerts.

MCP Tools (17)

Tool

Description

start_session

Start a new audit session for an agent

end_session

End a session and compute final aggregates

get_session

Get session details with aggregate metrics

list_sessions

List sessions with optional agent/active filters

record_call

Record a completed tool call (primary ingestion)

get_call

Look up a specific tool call by ID

query_calls

Search calls with flexible filters

log_event

Log a structured trace event (sub-step)

query_events

Query trace events with filters

get_stats

Aggregate statistics (error rate, percentiles, cost)

get_agent_report

Comprehensive per-agent performance report

get_cost_breakdown

Cost analysis grouped by tool/server/session

create_alert_rule

Set threshold-based alert rules

list_alert_rules

List configured alert rules

delete_alert_rule

Remove an alert rule

evaluate_alerts

Check which alert rules are currently breached

get_audit_summary

High-level dashboard summary

Alert Rules

Set up automatic monitoring:

engine.create_rule(
    name="high_error_rate",
    metric="error_rate",       # error_rate | p95_latency | cost_per_call | total_cost | call_volume
    operator=">",              # > | >= | < | <= | ==
    threshold=50.0,            # threshold value
    window=100,                # evaluate last N calls
)

engine.create_rule(
    name="budget_exceeded",
    metric="total_cost",
    operator=">=",
    threshold=10.0,
)

# Check if any rules are breached
alerts = engine.evaluate_rules()

Architecture

┌─────────────────────────────────────────────────────┐
│                  AI Agent (Claude, etc.)              │
│                                                       │
│  ┌──────────┐  ┌──────────┐  ┌───────────────────┐  │
│  │ MCP Tool │  │ MCP Tool │  │   mcp-audit       │  │
│  │ Server A │  │ Server B │  │   (this server)   │  │
│  └────┬─────┘  └────┬─────┘  └────────┬──────────┘  │
│       │              │                  │             │
│       └──────┬───────┘                  │             │
│              │  Agent calls record_call │             │
│              └──────────────────────────┘             │
└─────────────────────────────────────────────────────┘

The agent calls tools on other MCP servers, then calls record_call on mcp-audit to log what happened. Alternatively, wrap tool calls programmatically using the traced_call context manager.

Development

git clone https://github.com/nyx-builds/mcp-audit.git
cd mcp-audit
uv venv .venv
VIRTUAL_ENV=$(pwd)/.venv uv pip install -e ".[dev]"
.venv/bin/python -m pytest -q

License

MIT

A
license - permissive license
-
quality - not tested
B
maintenance

Maintenance

Maintainers
Response time
Release cycle
1Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nyx-builds/mcp-audit'

If you have feedback or need assistance with the MCP directory API, please join our Discord server