ZKStamp Proof-100
Server Details
Shielded proof-of-existence timestamps on BitcoinZ (zk-SNARKs). Free trial: 3 proofs.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- ZKStamp/Proof100
- GitHub Stars
- 0
- Server Listing
- Proof-100 MCP Server
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 3 tools
check_balance is clearly a different operation, and the two stamping tools are explicitly cross-referenced: timestamp_fingerprint takes an existing SHA-256 hex string while timestamp_text hashes short text server-side. That said, they perform essentially the same underlying action, so an agent must read the descriptions (not just the names) to pick correctly.
All three tools follow the same verb_noun shape (check_balance, timestamp_fingerprint, timestamp_text), with 'timestamp' used consistently as the action verb for the proof-creation family. No mixed conventions or casing inconsistencies.
Three tools is a tight, well-scoped surface for a narrow service: balance/credits, plus one entry point per accepted input type. It borders on thin, but each tool earns its place and nothing redundant is exposed.
The core lifecycle—check credits, acquire more, create a proof—is fully covered, with clear error semantics and returned artifacts (txid, viewing_key, explorer link). The only gap is that verification is pushed entirely to an external ZCheck tool and there is no way to list or re-fetch past proofs.
Available Tools
3 toolscheck_balanceAInspect
Show how many Proof-100 proofs are left and the two BTCZ deposit addresses for buying more: deposit_address (shielded zs, fully private) and t_deposit_address (transparent, for exchanges and t-only wallets like Coinomi; the payment is visible on the blockchain, the proofs stay shielded). 500,000 BTCZ to either (or both together) = 100 proofs after 2 confirmations.
Inputs: no named parameters.
timestamp_fingerprintAInspect
Create a private, dated proof that a file or data existed, without sending the data. Use this when you already have the SHA-256 fingerprint (hash) of a file; for a short text, use timestamp_text instead. Compute the hash locally over the exact bytes (for example: sha256sum MyFile.pdf) and pass the 64-character hex string. The fingerprint is written into the encrypted memo of a shielded (zk-SNARK) BitcoinZ transaction, sent to a new address made for this proof only; the block timestamp dates it. Takes about 10 to 60 seconds and uses 1 proof from the account (requires the account key in the Authorization header). Returns ok, txid, viewing_key, explorer link and proofs_left. Tell the user to keep the txid and viewing_key: together they let anyone verify this one proof with ZCheck, and reveal nothing else. On error (invalid fingerprint, invalid key, no proofs left, send failed) no proof is used.
Inputs: fingerprint (required).
timestamp_textAInspect
Compute the SHA-256 fingerprint of a short text on the Proof-100 server (the text is not stored), then write that fingerprint privately on the BitcoinZ blockchain. Returns the fingerprint, the transaction ID and a viewing key for this one proof. Keep the viewing key: with the txid it reveals this proof only. Uses 1 proof.
Inputs: text (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Prove a web page or document existed on a date: public SHA-256 registry anchored in Bitcoin. Free.
Timestamp & verify evidence on-chain, free. Proofpack: a portable BEEF+BUMP proof bundle per txid.
Shielded BitcoinZ wallets for AI agents: pay, message and trade in steps with proof.
Timestamp files in Bitcoin (OpenTimestamps): send a hash, pay per hash with x402, get a proof.
Related MCP Servers
AlicenseAqualityBmaintenanceZero-auth cryptographic notarization and PoE (Proof-of-Existence) layer on the TON Blockchain for AI outputs, smart contract audits, and agreements.41MIT- AlicenseAqualityBmaintenanceOTrust issues cryptographic PDRs (Provenance Data Records) — proving a digital artifact existed at a specific time. $0.01 per proof. Blockchain-anchored. Publicly verifiable.451MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to timestamp files in Bitcoin by submitting only their SHA-256 hashes, paying per hash in USDC via x402, and retrieving or verifying OpenTimestamps .ots proofs without an account or API key.MIT
- AlicenseAqualityBmaintenanceStamp, upgrade, and verify Bitcoin timestamps via AI agents using the OpenTimestamps protocol. No API keys required.980 npm3MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.