Skip to main content
Glama

Server Details

Shielded proof-of-existence timestamps on BitcoinZ (zk-SNARKs). Free trial: 3 proofs.

Ownership verified
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

A4.1/5.0

Scored across 3 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count4/5

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.

Completeness4/5

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 tools
check_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

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.