Skip to main content
Glama
namakoo-dev

nagi-ledger

by namakoo-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to nagi-ledger

No user-submitted related servers found.

    Related Servers

    • @agent-audit/mcp-server

      xueca
      A
      license
      A
      quality
      B
      maintenance
      MCP server that provides structured audit logging for AI agent repair tasks via tools to start, record, end, query, and export event traces, with JSONL persistence and SDK integration.
      5
      5 npm
      MIT

    • akm-mcp

      An-idd
      A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server enables AI agents to manage artifacts across sessions by providing tools for searching, retrieving, and registering entries in a persistent ledger, ensuring consistency and traceability of agent outputs.
      MIT

    • agent-activity

      patrickdaj
      A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server that exposes local coding-agent session logs as three tools for introspection of recent work, debugging tool failures, and tracking token usage and estimated cost without parsing log files.
      3
      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

    • 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
    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.6/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct domain object: general actions, subagent dispatches, verdicts, task status, and approaches. No two tools perform the same function, and the descriptions make the boundaries clear, even where overlap might occur (e.g., log_action vs log_approach).

    Naming Consistency3/5

    The consistent 'ledger_' prefix is good, but the suffix pattern is mixed: some tools use verb_noun (log_action, log_dispatch, log_verdict, log_approach, check_approaches) while others use noun_noun (task_status, session_report) or a bare noun (stats). This inconsistency makes the set slightly less predictable.

    Tool Count5/5

    Eight tools is well within the ideal range for a specialized audit ledger. The set includes both write and query operations without unnecessary redundancy or bloat, and each tool earns its place.

    Completeness5/5

    The surface provides comprehensive coverage for the domain: writing actions, dispatches, verdicts, and approaches, plus reading and aggregating that data. There are no obvious gaps; the append-only nature of the ledger is appropriate and fully supported.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources