Skip to main content
Glama
CSOAI-ORG

Agent Audit Logger MCP

by CSOAI-ORG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Agent Audit Logger MCP

No user-submitted related servers found.

    Related Servers

    • GoLogX (logx-mcp)

      AyoubTadlaoui
      A
      license
      Not graded
      quality
      C
      maintenance
      Tamper-evident audit logging for AI agents. Append-only, hash-chained, optionally Ed25519-signed log. The MCP server lets an agent keep and verify a record of what it actually did.
      7
      MIT

    • mcp-audit-gateway

      elang2
      A
      license
      Not graded
      quality
      A
      maintenance
      Tamper-evident audit trail for AI agent tool calls. Cryptographically signed, hash-chained records that prove what your agents did.
      3
      33 npm
      MIT

    • QuantaOptima

      jdhart81
      A
      license
      A
      quality
      B
      maintenance
      MCP server that provides cryptographic audit trails for AI agent actions, making every action tamper-evident via HMAC-SHA256 signed hash chains.
      10
      Apache 2.0

    • mcp-context-receipts

      DARREN-2000
      A
      license
      B
      quality
      B
      maintenance
      Privacy-first, tamper-evident receipts for MCP tool calls. It hashes and signs arguments/results so you can verify what ran, when, without storing raw payloads.
      2
      MIT
    • Proofpane by Proofpane

      Proofpaneofficial

      Proofpane
      A
      license
      B
      quality
      A
      maintenance
      A governance proxy for AI tools — every MCP/agent tool call is policy-gated, secret-redacted, and written to a hash-chained, offline-verifiable audit trail.
      13
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a unique and well-defined purpose: logging, searching, daily stats, attestation, and chain verification. No two tools overlap in functionality.

    Naming Consistency3/5

    Naming is a mix: 'daily_stats' uses noun_verb, 'log' and 'search' are single verbs, while 'sign_day_attestation' and 'verify_chain' follow a verb_noun pattern. This inconsistency is noticeable but not chaotic.

    Tool Count5/5

    With 5 tools, the server covers the essential operations for an audit logging system: append, search, statistics, attestation, and verification. The count is well-scoped without being excessive.

    Completeness5/5

    The tool set provides a complete lifecycle for audit logging: log entry creation, querying, daily statistics, integrity attestation, and chain verification. No obvious gaps given the append-only nature of audit logs.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources