Skip to main content
Glama
dan8433-user

ledger

by dan8433-user
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ledger

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-evidence-ledger

      brianpelow
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server providing an append-only, hash-chained evidence ledger for agent actions, where every record is a tamper-evident receipt cryptographically bound to all prior records and persisted as human-readable JSONL local state. It exposes tools to append records, verify chain integrity (pinpointing tampering), query records by actor/action/target/time, and fetch ledger stats—with no update or delete capabilities by design.
      1
      Apache 2.0

    • AgentAudit MCP

      Rumblingb
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides an immutable, tamper-evident audit trail for AI agents, enabling event logging with cryptographic chaining, search, verification, and statistics.
      2
      MIT

    • action-ledger

      SweetKenneth
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables recording agent proposals, executions, redactions and annotations into an append-only, hash-linked evidence chain, then exporting a self-contained range and verifying offline from the export's own bytes alone so a third party can check history without trusting the agent runtime or its storage.
      MIT

    • AgentSeal

      JoeyBrar
      A
      license
      A
      quality
      C
      maintenance
      Every agent action is recorded in a SHA-256 hash chain. Prove to clients that your agent did what it said it did. Record, query, verify, and export agent activity.
      3
      36 npm
      1
      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

    A4/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool targets a distinct part of the ledger lifecycle, but verification-related tools overlap in behavior: ledger_verify, prove_my_conduct, and verify_peer_ledger all return three-valued chain verdicts. The descriptions are explicit about local vs peer vs proof use cases, so an agent can disambiguate with care.

    Naming Consistency3/5

    Naming is mixed: ledger_append and ledger_verify use a noun_verb pattern, while prove_my_conduct, verify_peer_ledger, and declare_break use verb_noun patterns. All names are snake_case and readable, but the inconsistent structural convention makes the set less predictable.

    Tool Count5/5

    Five tools is well-scoped for a specialized ledger server. Each tool covers a meaningful operation without unnecessary bloat, and the count fits comfortably within the expected range for a focused tool set.

    Completeness3/5

    The core append, verify, declare-break, proof, and peer-verification operations are present, but there is no tool to export or read the local ledger as JSONL, which verify_peer_ledger explicitly consumes. This is a notable gap that forces agents to obtain the ledger text through out-of-band means.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources