Skip to main content
Glama
Sign In
Sovereign Agent Logbook

Sovereign Agent Logbook

by Delfen-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Sovereign Agent Logbook

No user-submitted related servers found.

    Related Servers

    • AgentAudit MCP

      Rumblingb
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides an immutable, tamper-evident audit trail for AI agents, enabling event logging with cryptographic chaining, search, verification, and statistics.
      3
      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
      19 npm
      MIT

    • Inficy

      artnames
      A
      license
      Not graded
      quality
      C
      maintenance
      Captures AI agent runs and turns them into tamper-evident execution records showing tool use, timing, failures, recoveries, and human interventions. Records can be inspected, exported, and verified offline.
      MIT

    • Dvarapala

      demolished-lab
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides permission gates and tamper-evident audit logging for AI agent tool executions, with declarative policies, consent ladders, and hash-chained verification.
      MIT

    • homestead-memory

      fuckbigtech-ai
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables capturing a tamper-evident, hash-chained local record of every AI agent tool call — both the decision before a tool runs and its outcome — so you can review what the agent actually did in order, detect edits, deletions, or reordering at the exact index, and export a signed evidence pack any third party can verify with no installs.
      31 PyPI
      2
      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

    A3.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool maps to a distinct operation on the logbook: log_event writes, recent_events reads a quick tail, verify_logbook checks hash-chain integrity, and export_logbook produces an auditor-facing dump. The write/read/verify/export split is unambiguous, and the only mild adjacency (recent_events vs export_logbook) is clearly differentiated by scope and format.

    Naming Consistency4/5

    All names use consistent snake_case and are built around the shared noun 'logbook'/'event'. Three tools follow a verb_noun pattern (log_event, verify_logbook, export_logbook), but recent_events deviates into an adjective_noun form, a minor inconsistency in an otherwise predictable scheme.

    Tool Count5/5

    Four tools is compact but well-matched to an append-only audit log with verification and export needs. Each tool earns its place: write, inspect, verify, and hand off to a human auditor, with no redundant or filler operations.

    Completeness4/5

    The core lifecycle of an audit logbook (record, inspect, verify integrity, export) is covered, and outcome re-logging handles status transitions without a separate update tool. Minor gaps remain: recent_events caps at a small tail with no paging or filtering by agent, seq, or time range, so the only way to traverse full history is the export dump.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources