Skip to main content
Glama

Related Servers

Alternatives to tersign

No user-submitted related servers found.

    Related Servers

    • F
      license
      D
      quality
      C
      maintenance
      MCP server for the Recite API, enabling receipt scanning, transaction management, batch processing, and local ledger workflows for agents.
      57
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Local MCP server that signs and records agent actions into a tamper-evident log using Ed25519 keys for frictionless integration with Touchstone.
      33 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that provides append-only, tamper-evident local receipts for AI agent actions, capturing command executions, outputs, and handoff evidence.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides evidence-oriented MCP service for cryptographically identified agents, bounded public contracts, privacy-preserving records, and append-only audit.
      Apache 2.0
    • 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that acts as a temporal verification firewall, checking structured assumptions or diffs against immutable version receipts to return allow/block/abstain with cited evidence.
      MIT

    TDQS

    A4.5/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clear operational boundary: payment receipt issuance and refunds are distinct from disclosure recording, and verification tools are split by artifact type. The dispute tools form a separate, well-defined lifecycle, and the descriptions actively cross-reference the correct counterpart tool.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case convention. Verification, recording, and dispute actions use predictable verbs, and the multiword nouns are consistently descriptive.

    Tool Count5/5

    Nine tools is well-scoped for the stated domain. Each tool corresponds to a necessary step in the receipt, compliance, refund, or dispute workflow with no redundant helpers or superficial wrappers.

    Completeness5/5

    The surface covers the full intended lifecycle: issue and verify payment receipts, record and verify disclosures, handle refunds, and open, evidence, adjudicate, and fetch disputes. The append-only design makes updates/deleties unnecessary, and the returned artifacts avoid dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues