Skip to main content
Glama
Sign In
verify-proof

verify-proof

Official
by Fulcrum-Enterprises
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to verify-proof

No user-submitted related servers found.

    Related Servers

    • satsignal-mcp

      Steleet
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables tamper-evident anchoring of file, text, or JSON hashes to the BSV blockchain via MCP tools, with verification and lookup capabilities.
      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

    • verify-mcp

      ScopeBlind
      A
      license
      A
      quality
      C
      maintenance
      MCP server for offline verification of signed artifacts — receipts, manifests, and audit bundles. MIT licensed, works without accounts or API calls. Tools: self_test, verify_receipt, verify_bundle, explain_artifact.
      4
      95 npm
      6
      Apache 2.0

    • Web Resource Ledger

      benpeter
      A
      license
      Not graded
      quality
      C
      maintenance
      📇 ☁️ - Capture web pages as cryptographically signed, tamper-evident evidence. Ed25519 signatures, RFC 3161 timestamps, and WACZ archives. Four tools: capture_url, get_capture, list_captures, verify_capture.
      2 npm
      2
      MIT

    • otskit-mcp

      OTSkit
      A
      license
      A
      quality
      A
      maintenance
      Stamp, upgrade, and verify Bitcoin timestamps via AI agents using the OpenTimestamps protocol. No API keys required.
      9
      147 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
    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

    A4.4/5.0

    Scored across 5 tools

    Disambiguation4/5

    Most tools have distinct actions: compute, explain, create, verify. The only real ambiguity is between verify_file and verify_hash, which both verify a proof and differ mainly in whether input is a file path or a precomputed hash; a weak agent might select the wrong one.

    Naming Consistency5/5

    All tool names follow the same lowercase verb_noun pattern: compute_file_hash, explain_proof, create_proof, verify_file, verify_hash. The repeated verify verb is consistently disambiguated by the object (file vs hash).

    Tool Count5/5

    Five tools is well-scoped for the domain of blockchain timestamp proofs. Each tool covers a meaningful step in the workflow and none feels redundant or unnecessary.

    Completeness3/5

    The set covers hashing, proof creation, explanation, and verification, but there is a notable integration gap: create_proof returns only a summary and URLs, while verify_file, verify_hash, and explain_proof all require a proof JSON file. A user who creates a proof cannot directly verify it within the toolset unless they obtain the proof JSON externally.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources