Skip to main content
Glama
Sign In
DMT Receipts

DMT Receipts

by Colchora
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to DMT Receipts

No user-submitted related servers found.

    Related Servers

    • otskit-mcp

      OTSkit
      A
      license
      A
      quality
      B
      maintenance
      Stamp, upgrade, and verify Bitcoin timestamps via AI agents using the OpenTimestamps protocol. No API keys required.
      9
      140 npm
      3
      MIT

    • APEX PSI MCP Server

      kawal393
      A
      license
      A
      quality
      B
      maintenance
      Append-only evidence receipts for AI records: seal, verify, cite, chain-check, anchor status. A seal proves a record existed at a time, not that its contents are true. Five tools over stdio with npx -y apex-psi-mcp — no account, no key, verification free forever.
      5
      316 npm
      1
      MIT
    • Orphograph

      Orphographofficial

      Orphograph
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents and MCP hosts to anchor file hashes to Bitcoin via OpenTimestamps and verify proofs, ensuring files existed before a given time with privacy-preserving local hashing.
      MIT
    • Proof-100 MCP Server

      Proof-100 MCP Serverofficial

      ZKStamp
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to timestamp SHA-256 fingerprints or short text on the BitcoinZ blockchain via shielded transactions, returning transaction IDs and viewing keys, and to check proof balance and deposit address.
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are cleanly complementary: stamp_memory creates a receipt, verify_receipt checks one. There is no overlap and the descriptions make the create/verify split explicit.

    Naming Consistency5/5

    Both names follow a strict verb_noun snake_case pattern (stamp_memory, verify_receipt). The convention is predictable and directly reflects each tool's action and target.

    Tool Count4/5

    Two tools is thin in absolute terms, but the server's scope is deliberately narrow — stamp a memory and verify a receipt — and each tool clearly earns its place. Nothing superfluous is present.

    Completeness3/5

    The basic stamp/verify lifecycle is covered, but verify_receipt only checks header/digest consistency and explicitly does not validate calendar operations or Bitcoin inclusion, leaving agents to invoke external ots upgrade/verify for the real proof. No status lookup or receipt introspection is offered, though the stateless design limits what could be added.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources