Verifile
Server Details
Proof of existence for files and texts: anchor a SHA-256 on the Doichain and verify it later
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- neubuot/doichain-mcp
- GitHub Stars
- 0
- Server Listing
- Doichain MCP Server
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: anchor_proof writes an anchor, check_proof reads proof status, get_anchoring_quota reports remaining quota, and hash_text computes a SHA-256 digest. No two tools can be reasonably confused for the same operation.
All tool names use consistent snake_case verb_noun patterns: anchor_proof, check_proof, get_anchoring_quota, hash_text. The naming is predictable and readable throughout.
Four tools are well-scoped for a focused proof-anchoring service: compute hash, anchor proof, check proof, and check quota. Each tool earns its place without bloat.
The surface covers the full lifecycle: local/server hashing, anchoring a hash, checking proof status including expiry and re-registration, and quota awareness. No obvious operational gap exists for the stated domain.
Available Tools
4 toolsanchor_proofAnchor a proof of existenceAIdempotentInspect
Anchor a SHA-256 hash on the Doichain as a tamper-evident timestamp (proof of existence, name poe/). Free for users, limited per IP address and day (see get_anchoring_quota). Confirms with the next block, usually within 10 minutes, then check_proof returns block height and time. If the hash is already anchored or pending, the existing proof is returned instead of creating a second one. If an earlier proof of the hash has expired, it stays valid and is returned with expired true. Nothing is registered unless reanchor_expired is true. Only the hash and the optional note and file name become public, never the document itself. The operator of this server pays for the name and holds it. The proof shows that a document with this hash existed no later than the block time, not who submitted it.
Inputs: sha256 (required), note, filename, reanchor_expired. Returns: object
check_proofCheck a proof of existenceARead-onlyIdempotentInspect
Check whether a SHA-256 hash is anchored on the Doichain (name poe/) and since when. Returns status (confirmed, pending, expired, unknown) and at the top level block height, block time, transaction and links of the first anchoring, which is the proof time. If the name was updated later or registered again after it expired (possibly by someone else), that registration is reported separately in latest_registration with its own holder and record, which are not part of the original proof. A confirmed or expired proof shows that a document with exactly this hash existed no later than the block time, not who submitted it.
Inputs: sha256 (required). Returns: object
get_anchoring_quotaRemaining anchoring quotaARead-onlyIdempotentInspect
How many proofs can still be anchored today (UTC day) within the free public quota for the caller's IP address. Hosted chat apps connect from their own servers, so their users share one quota. Callers that send their own API key in the X-API-Key header have no quota.
Inputs: no named parameters. Returns: object
hash_textSHA-256 of a textARead-onlyIdempotentInspect
Compute the SHA-256 digest of a short text (UTF-8) on the server, for example to anchor a statement or a message with anchor_proof. The text is sent to the server but not stored or logged. For files and for confidential texts compute the hash locally instead (sha256sum file, or Get-FileHash -Algorithm SHA256).
Inputs: text (required). Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Proof of existence, names and chain data of the Doichain blockchain for AI agents
Proof of existence for files: anchor a SHA-256 hash on Base, look up proofs. Paid with x402.
Prove a web page or document existed on a date: public SHA-256 registry anchored in Bitcoin. Free.
Pay-and-anchor a hash or AI decision log on Cardano (CIP-0190). Non-custodial. MCP-native. Mainnet.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenancePost-quantum document anchoring for AI agents. Anchor any SHA-256 hash to Algorand mainnet with ML-DSA-65 (NIST FIPS-204) signatures and receive a self-contained proof bundle verifiable offline — decades from now, without trusting any vendor.13 npm1MIT
- 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 gradedqualityBmaintenanceEnables 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-proofofficial
AlicenseAqualityBmaintenanceVerifies blockchain-anchored timestamp proofs entirely on the user's machine, with five tools: hash a file, verify a file against a proof, verify a known hash against inline proof data, explain what a proof asserts, and create a new proof through ProofLedger. Verification recomputes the SHA-256 and walks the Merkle path locally instead of asking the issuer; only create uses the network.568 PyPIMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.