verify-proof
OfficialRelated Servers
Alternatives to verify-proof
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables tamper-evident anchoring of file, text, or JSON hashes to the BSV blockchain via MCP tools, with verification and lookup capabilities.MIT

Orphographofficial
AlicenseNot gradedqualityAmaintenanceEnables 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- AlicenseAqualityCmaintenanceMCP 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.462 npm6Apache 2.0
- AlicenseNot gradedqualityFmaintenance📇 ☁️ - 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.1 npm1MIT
- AlicenseAqualityAmaintenanceStamp, upgrade, and verify Bitcoin timestamps via AI agents using the OpenTimestamps protocol. No API keys required.2995 npm3MIT
- AlicenseAqualityBmaintenanceProvides 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.5245 npm1MIT
TDQS
Scored across 5 tools
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.
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).
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.
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.