ZKStamp Proof-100 MCP server
Commit Oct 29, 2026Writes SHA-256 fingerprints to the BitcoinZ blockchain using zk-SNARKs to provide shielded, dated proofs of existence.
Also known as ZKStamp/Proof100, proof100
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.2.0
- Last commit
- Oct 29, 2026
- License
- MIT
What is ZKStamp Proof-100 MCP?
ZKStamp Proof-100 writes SHA-256 fingerprints to the BitcoinZ blockchain using zk-SNARKs to provide shielded, dated proofs of existence.
Summary generated from the project's README
About ZKStamp Proof-100 MCP server
ZKStamp Proof-100 provides a way to create dated, shielded proofs of existence for digital files using the BitcoinZ blockchain. By submitting a SHA-256 fingerprint, users can record a timestamped record that remains private through zk-SNARK technology. This ensures that neither the fingerprint nor the identity of the creator is visible on the public blockchain. The service is designed for developers and AI agents who need to verify that a specific piece of data existed at a certain time without revealing the data itself.
Users interact with the service via a REST API or an MCP endpoint. To use it with an AI client like Claude, you must provide an authorization header containing your unique API key. The system operates on a prepaid model where users purchase packs of 100 proofs using BTCZ. New accounts can access a limited free trial of three proofs. Once a proof is created, the server returns a transaction ID and a viewing key, which are required to verify the fingerprint later using the ZCheck script on a local BitcoinZ node.
What you can do with it
- 1Verify document integrityA developer can use the ZCheck script to confirm if a file has been altered by comparing it against the blockchain record.
Written from the project's README. Every use case is checked against a quote from it.
How to install ZKStamp Proof-100 MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall ZKStamp Proof-100 MCP in Claude Code
$ claude mcp add --transport http proof100 https://proof.zketernity.app/mcpInstall ZKStamp Proof-100 MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"proof100": {
"url": "https://proof.zketernity.app/mcp"
}
}
}Install ZKStamp Proof-100 MCP in VS Code
.vscode/mcp.json
{
"servers": {
"proof100": {
"type": "http",
"url": "https://proof.zketernity.app/mcp"
}
}
}Install ZKStamp Proof-100 MCP in VS Code CLI
$ code --add-mcp '{"name":"proof100","type":"http","url":"https://proof.zketernity.app/mcp"}'Install ZKStamp Proof-100 MCP in Codex
$ codex mcp add proof100 --url https://proof.zketernity.app/mcpInstall ZKStamp Proof-100 MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.proof100] url = "https://proof.zketernity.app/mcp"
Install ZKStamp Proof-100 MCP in Gemini CLI
$ gemini mcp add -s user --transport http proof100 https://proof.zketernity.app/mcpInstall ZKStamp Proof-100 MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"proof100": {
"url": "https://proof.zketernity.app/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablezkstamp/proof100 is public and reachablegithub.com/zkstamp/proof100 ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-29github.com/zkstamp/proof100 ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 100 msPass
README
View on GitHubZKStamp · Proof-100
Stamp it with Z. Before Q.
🎬 Watch the 60-second demo: an AI agent stamps an idea, then ZCheck says VALID, and NOT VALID with one letter changed
Proof-100 writes the SHA-256 fingerprint of any file to the BitcoinZ blockchain in a shielded (zk-SNARK) transaction. You get a dated proof that the file existed, and nobody on the blockchain can see the fingerprint or who made it.
- ZKStamp is the brand.
- Proof-100 is what you buy: a pack of 100 proofs.
- ZCheck is how you check: a small script that verifies a proof on your own BitcoinZ node.
Service: https://proof.zketernity.app · For AI agents: /llms.txt
How it works
- You send a fingerprint (SHA-256, 64 hex characters). Your file never leaves your machine.
- The server writes
PROOF100 sha256:<fingerprint>into the encrypted memo of a shielded BitcoinZ transaction, sent to a brand-new address made for this one proof. - You get back the transaction ID and that address's viewing key.
- The block's timestamp dates your proof.
- To prove it later, give someone the transaction ID + viewing key. With ZCheck, they read the fingerprint straight from the blockchain and compare it with your file. They see this one proof and nothing else.
Keep your viewing key. Without it, that proof cannot be revealed.
Quick start (API)
Base URL: https://proof.zketernity.app
1. Create an account (your key is shown once, so save it):
curl -s -X POST https://proof.zketernity.app/v1/account
Returns key (starts with p100_), deposit_address (shielded, zs) and t_deposit_address (transparent, t).
Free trial: new accounts get 3 free proofs, no payment needed (limited to 13 new trial accounts per day, until 27 November 2026). The response shows free_proofs.
2. Buy proofs: send 500,000 BTCZ to either address, or split it across both. After 2 confirmations, 100 proofs are credited automatically.
deposit_address(zs): fully private payment. Paying to the zs address? Use Z-TEXT or a full-node wallet. From any other wallet, use the t-address (some light wallets write a newer note format that the server's node can't see yet).t_deposit_address(t): for exchanges and t-only wallets like Coinomi. Your payment is visible on the blockchain, but your proofs stay fully shielded. The server moves these coins to the shielded side by itself (the operator pays that 0.0001 BTCZ fee).
3. Check your balance:
curl -s https://proof.zketernity.app/v1/balance -H "Authorization: Bearer YOUR_KEY"
4. Make a proof:
FP=$(sha256sum MyFile.pdf | cut -d' ' -f1)
curl -s -X POST https://proof.zketernity.app/v1/proof \
-H "Authorization: Bearer YOUR_KEY" \
-H "Content-Type: application/json" \
-d "{\"fingerprint\": \"$FP\"}"
Returns txid, viewing_key and proofs_left. A proof takes about 10 to 60 seconds.
The key is accepted as Authorization: Bearer <key> (with or without the space) or as X-API-Key: <key>.
For AI agents (MCP)
Proof-100 speaks MCP at:
https://proof.zketernity.app/mcp
Tools:
| Tool | What it does |
|---|---|
timestamp_fingerprint |
Timestamp a SHA-256 fingerprint. Returns txid + viewing key. |
timestamp_text |
The server hashes a short text (the text is not stored) and timestamps the fingerprint. |
check_balance |
Proofs left and your deposit address. |
In Claude: add a custom connector with that URL, choose no sign-in, and add the request header Authorization = Bearer YOUR_KEY.
Verify a proof with ZCheck
You need a synced BitcoinZ node, Python 3, the original file, the txid and the viewing key.
python3 zcheck/ZCheck.py --txid <txid> --viewing-key <zxviews...> --file MyFile.pdf
Answers:
VALID: this exact fingerprint was written on the BitcoinZ blockchain in block N, on <date> UTCNOT VALID: ... holds a different fingerprint(the file was changed)
The first run scans the chain from block 1,862,000 for that viewing key, which can take a few minutes. Options: --cli (path to bitcoinz-cli), --datadir, --start-height, or --fingerprint instead of --file.
Price
500,000 BTCZ for 100 proofs, paid in BTCZ only. No card, no email, no account name. One proof costs 5,000 BTCZ: a fraction of the price of a €2 coffee. ☕
Coming from an exchange, or from a wallet that only sends to t-addresses (like Coinomi)? Pay your t_deposit_address directly. For a fully private payment, send your BTCZ to the free Z-TEXT wallet first: it shields them automatically. Then pay from Z-TEXT to your zs deposit address.
Questions, or no BTCZ yet? Write to contact@z-text.com. We'll help you find where to get BTCZ.
Trust model and honest limits
- What the blockchain hides: the fingerprint, the addresses and the amounts are inside a shielded transaction. Block explorers show only that a transaction exists.
- What the server sees: the operator's server receives your fingerprint (and, for
timestamp_text, your text) when you submit it. It does not log fingerprints or texts, and it does not store which proof belongs to which account. You can read the code in this repository. - One operator, one server: if the server is down, no new proofs can be made. Existing proofs stay on the blockchain and remain verifiable with ZCheck on any BitcoinZ node.
- Quantum: the SHA-256 fingerprint and its date are expected to hold up well against quantum computers. The privacy of shielded transactions relies on today's zk-SNARK cryptography, which is not post-quantum. A future quantum computer could, in theory, read old memos, which would reveal fingerprints (never files).
- BitcoinZ is a small chain with thin trading volume. Factor that in for high-stakes uses.
Self-hosting
server/: the code that runs the service (Python 3, Flask).Proof100Core.py: accounts, payment watch, making proofsProof100Api.py: REST API and MCP endpoint (listens on 127.0.0.1:5100)CheckPayments.py,CreateAccount.py,HealthCheck.pyGrantProofs.py: operator tool, creates an account with free proofs (for testers)
deploy/: example systemd units, nginx site and config templates.zcheck/ZCheck.py: the verifier.
Requirements: a synced BitcoinZ node (2.3.1 or later) with a funded shielded address, Python 3 with flask and requests, and nginx with a TLS certificate. Never commit Proof100Config.json, the database, or any key.
Related
I Am Wallet: shielded BitcoinZ wallets for AI agents, same operator. Agents pay and send private messages to each other, by themselves (llms.txt).
Contact
contact@z-text.com (Z-TEXT LLC)
License
MIT. See LICENSE.
ZKStamp Proof-100 MCP questions
How do I add ZKStamp Proof-100 MCP to Claude Code?
Run claude mcp add --transport http proof100 https://proof.zketernity.app/mcp in your terminal. Add --scope user to make it available in every project.
How do I add ZKStamp Proof-100 MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Does the server see my actual files?
No, you only send a SHA-256 fingerprint to the server, so your file never leaves your machine.