Skip to main content
Glama
arults

ActSeal MCP

by arults
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to ActSeal MCP

No user-submitted related servers found.

    Related Servers

    • pcrzero-mcp

      Scytalex-LLC
      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

    • APEX PSI MCP Server

      kawal393
      A
      license
      A
      quality
      B
      maintenance
      Provides cryptographic truth infrastructure for AI agents, enabling them to seal content with SHA-256 and Ed25519, verify receipts, anchor them to Bitcoin via OpenTimestamps, generate citations, and audit chains of receipts.
      5
      59 npm
      1
      MIT

    • agent-receipts-mcp

      dhanushs1912-svg
      A
      license
      A
      quality
      C
      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
      26 npm
      1
      MIT

    • hive-mcp-sigr

      srotzin
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to sign and verify actions with ML-DSA-65 digital signatures, providing tamper-proof receipts that can be verified offline without any secrets.
      MIT

    • ArtifactGuard

      blackcow4234-lab
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to validate deliverables (JSON, ZIP, PDF, DOCX) against signed contracts, generating verifiable receipts with Ed25519 signatures.
      -

    • actionproof

      Burakfenerci5
      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
      30 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    issue_receipt and verify_receipt have clearly opposite, non-overlapping purposes (creation vs. validation), and the descriptions reinforce the distinction. An agent can select between them with no ambiguity.

    Naming Consistency5/5

    Both tools follow the same snake_case verb_noun pattern (issue_receipt, verify_receipt). The naming is fully predictable and symmetric.

    Tool Count4/5

    Two tools is thin for a general-purpose server, but for the narrow domain of issuing and verifying signed receipts the pair is reasonably scoped. It sits just under the typical comfortable range rather than being an extreme mismatch.

    Completeness4/5

    The core lifecycle (issue then verify) is fully covered with no dead ends for the primary workflow. Minor gaps exist, such as listing receipts or revoking/invalidating one, which agents would have to work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources