Skip to main content
Glama
getAlby

OpenTimeStamps MCP Server

by getAlby
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to OpenTimeStamps MCP Server

No user-submitted related servers found.

    Related Servers

    • @unfakable/mcp

      unfakable
      A
      license
      A
      quality
      D
      maintenance
      Document verification MCP server enabling AI agents to verify file authenticity by computing SHA-256 fingerprints locally and checking Bitcoin-anchored proofs via OpenTimestamps.
      5
      5 npm
      MIT
    • Orphograph by 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

    • Mempool MCP Server

      alexandresanlim
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides real-time Bitcoin blockchain and mempool data to AI clients, allowing access to comprehensive Bitcoin network information through various data tools.
      31
      4 npm
      5
      MIT

    • Nostr MCP Server

      mikeysrecipes
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI models to interact with the Nostr network, allowing them to post notes and eventually send Lightning zaps to users.
      24 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.3/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool maps to a distinct step in the OpenTimestamps workflow (hash, stamp, load, info, upgrade, verify, retrieve). The only potential overlap is load_proof vs get_full_proof, but their descriptions distinguish inputs (hex/file vs hash), so confusion is limited.

    Naming Consistency5/5

    All tool names use snake_case with a verb-first pattern (calculate_hash, stamp_hash, load_proof, upgrade_proof, verify_proof, etc.). The naming is predictable and consistent across the set.

    Tool Count5/5

    Seven tools is well-scoped for the OpenTimestamps lifecycle; each operation serves a distinct purpose without redundancy. The count fits comfortably within the recommended 3–15 range.

    Completeness4/5

    Core lifecycle operations—hashing, stamping, loading/retrieving proofs, inspecting, upgrading, and verifying—are all covered. A minor gap is the lack of an explicit save/export proof tool, though load_proof and get_full_proof may cover retrieval needs.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources