Skip to main content
Glama
dhanushs1912-svg

agent-receipts-mcp

Related Servers

Alternatives to agent-receipts-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Issue and verify signed receipts for agent actions, enabling durable, independently checkable proof of policy decisions. Supports offline verification via get_keyset and verify_receipt tools without an account.
      0
      Inno Setup
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to create cryptographically verifiable receipts of their delegated work, with capabilities for multi-party approval and offline verification.
      11
      50 npm
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      Gives AI agents verifiable, tamper-evident receipts for their actions — attest_action signs a cryptographic receipt for what the agent did (email sent, payment made, form filed), verify_receipt checks it offline, get_identity returns the agent's did:key. Sign locally, verify anywhere, zero backend.
      3
      49 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Issues accountable identities for AI agents before they interact with tools, with tools for identity management and receipt export.
      -
    • A
      license
      A
      quality
      A
      maintenance
      Post-quantum, tamper-evident receipts for consequential agent actions. Provides tools for auditing, gating decisions, and egress classification with quantum-hardened security.
      7
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to sign decisions with post-quantum cryptographic proofs and maintain secure audit trails for compliance. It provides tools for stamping events, verifying chain integrity, and exporting audit data across industries like finance and healthcare.
      4
      30 npm
      MIT

    TDQS

    A4.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct purpose: create, verify, export, and service info. No overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (issue_receipt, verify_receipt, export_audit_bundle, get_service_info), using snake_case throughout.

    Tool Count5/5

    Four tools is well-scoped for a focused domain, covering the core receipt lifecycle without redundancy or bloat.

    Completeness4/5

    The set covers creation, verification, and export, which aligns with the immutable audit receipt purpose. Missing a direct single-receipt fetch is a minor gap since export covers bulk retrieval.

    Maintenance

    ActivityStale
    ResponsivenessNo issues