Skip to main content
Glama

Related Servers

Alternatives to signafaide

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Tamper-evident audit trail for AI agent tool calls. Cryptographically signed, hash-chained records that prove what your agents did.
      3
      29 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      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.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Tamper-evident recorder for AI agent tool calls. Every MCP call is written to a hash-chained, signed log the agent cannot edit, delete or hide; anyone can verify the chain offline.
      Apache 2.0
    • 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
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents and their hosts to record actions, tool calls, and human approvals in an append-only, hash-chained log; verify tamper evidence; mask secrets; retrieve recent events; and export audit-ready JSON or CSV on self-hosted infrastructure.
      4
      192 PyPI
      Apache 2.0
    • 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.
      8
      MIT

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation3/5

    signafaide_setup and signafaide_quickstart overlap heavily: both return an install command plus framework-specific integration code, differing mainly in that setup also detects the stack and previews actions. The claim link is surfaced by three tools (claim_link, status, and init's return), creating further boundary blur. init vs setup is at least clarified by descriptions (init is the real side-effecting call, setup is a read-only preview).

    Naming Consistency4/5

    Every tool uses the signafaide_ prefix with snake_case, which is predictable and easy to scan. Minor deviation: some names are verbs (verify, setup, init) while others are nouns (status, claim_link), but the meaning stays clear.

    Tool Count5/5

    Seven tools is well-matched to the scope: preview, initialize, quickstart, status, claim link, verify, and error explanation. Nothing feels padded, and no obvious operation is crammed into an overloaded tool.

    Completeness3/5

    The lifecycle of onboarding and verification is covered, but there is no tool to read, list, or search the actual recorded events, and no explicit way to ship pending outbox records (it happens implicitly inside verify). Rekey/rotate, unclaim/revoke, and cleanup of local .signafaide state are also absent, leaving a few dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues