Skip to main content
Glama
DARREN-2000

mcp-context-receipts

by DARREN-2000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mcp-context-receipts

No user-submitted related servers found.

    Related Servers

    • @humanaccepted/mcp

      Ola-Turmo
      F
      license
      A
      quality
      D
      maintenance
      MCP server that auto-emits tamper-evident receipts for every tool call, enabling EU AI Act Article 12 compliance with signed, chain-linked receipts.
      1
      -

    • Agent Audit Logger MCP

      CSOAI-ORG
      A
      license
      B
      quality
      C
      maintenance
      Hash-chained HMAC-signed audit log MCP for A2A (agent-to-agent) calls. Every tool-call, agent-handoff, decision gets a tamper-evident signed record.
      5
      167 PyPI
      MIT

    • ComputeLedger MCP Server

      RudrenduPaul
      A
      license
      A
      quality
      B
      maintenance
      Provides cryptographically signed, tamper-evident compute usage receipts via a Model Context Protocol server, exposing tools to record usage, verify receipts, list the ledger, and verify ledger integrity without requiring any account, API key, or single cloud provider.
      4
      4 npm
      Apache 2.0

    • 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
      31 npm
      MIT

    • agent-receipts-mcp

      dhanushs1912-svg
      A
      license
      A
      quality
      A
      maintenance
      Provides tools to issue, verify, and export cryptographically signed receipts for AI agent actions, enabling tamper-proof audit trails for compliance with regulations like the EU AI Act.
      4
      39 npm
      1
      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

    B3.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one creates a receipt and the other verifies it. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tool names follow the same verb_noun pattern: create_receipt and verify_receipt. The naming is consistent, predictable, and aligned with the server's purpose.

    Tool Count4/5

    With only two tools, the set is minimal, but each tool is essential and earns its place for the narrow domain of receipt creation and verification. It feels slightly thin but is still well-scoped.

    Completeness5/5

    The domain is signing and verifying receipts, and create plus verify covers the full lifecycle. No update or delete is expected for immutable receipts, so there are no meaningful gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources