Koskamo

ZKStamp Proof-100 MCP

A community MCP server that writes SHA-256 fingerprints of files or text to the BitcoinZ blockchain using shielded zk-SNARK transactions, providing dated proof of existence without revealing data or identity.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

ZKStamp Proof-100 MCP logo, by Z-TEXT LLCCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-01Published by Z-TEXT LLC
You need:send the account key as the header `Authorization: Bearer ` (or `X-API-Key: `)
MCP endpoint (Streamable HTTP)
https://proof.zketernity.app/mcp
Vendor documentation

What you can do with it

  • Timestamp a SHA-256 fingerprint of a file
  • Hash and timestamp short text securely
  • Check remaining proof balance and deposit addresses

Source and maintenance

Community listingRegistry 0.2.0
Maintenance checked

Protocol and capabilities

Server
Proof-100 0.1
MCP protocol
2025-06-18
Tools
3 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {}
}

Tools

3 advertised

timestamp_fingerprint
Advertised by the server during the last successful anonymous check.

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.

timestamp_fingerprint input schema
{
  "type": "object",
  "required": [
    "fingerprint"
  ],
  "properties": {
    "fingerprint": {
      "type": "string",
      "pattern": "^[0-9a-fA-F]{64}$",
      "description": "SHA-256 hash of the file, as 64 hexadecimal characters (case-insensitive), e.g. 968c796b7f8c9259ee92d7168d882df2f347d9711a51da90182c98d69139cdb7"
    }
  }
}
timestamp_text
Advertised by the server during the last successful anonymous check.

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.

timestamp_text input schema
{
  "type": "object",
  "required": [
    "text"
  ],
  "properties": {
    "text": {
      "type": "string",
      "description": "The exact text to timestamp"
    }
  }
}
check_balance
Advertised by the server during the last successful anonymous check.

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.

check_balance input schema
{
  "type": "object",
  "properties": {}
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
866 ms
95th percentile latency
866 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 866 ms · metadata changed · 3 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http zkstamp-proof-100-mcp https://proof.zketernity.app/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add zkstamp-proof-100-mcp --url https://proof.zketernity.app/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable zkstamp-proof-100-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "zkstamp-proof-100-mcp": {
      "url": "https://proof.zketernity.app/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "zkstamp-proof-100-mcp": {
      "type": "streamableHttp",
      "url": "https://proof.zketernity.app/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start zkstamp-proof-100-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "zkstamp-proof-100-mcp": {
      "type": "http",
      "url": "https://proof.zketernity.app/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http zkstamp-proof-100-mcp https://proof.zketernity.app/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "zkstamp-proof-100-mcp": {
      "url": "https://proof.zketernity.app/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "zkstamp-proof-100-mcp": {
      "serverUrl": "https://proof.zketernity.app/mcp"
    }
  }
}

Let your agent find its tools

Find servers like ZKStamp Proof-100 MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.