protogrid

Search / io.github.ZKStamp/proof100

ZKStamp Proof-100

R1· needs a key

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

v0.2.0 · active · repository · website · descriptor JSON · versions

An agent can connect on its own if it already holds PROOF100_TOKEN.Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.
Quality68needs work
Trust97of 100
Uptime, 30 days98%
Latency p50460 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "proof100": {
      "type": "http",
      "url": "https://proof.zketernity.app/mcp",
      "headers": {
        "Authorization": "Bearer ${PROOF100_TOKEN}"
      }
    }
  }
}
claude mcp add --transport http proof100 https://proof.zketernity.app/mcp --header "Authorization: Bearer ${PROOF100_TOKEN}"
[mcp_servers.proof100]
url = "https://proof.zketernity.app/mcp"
bearer_token_env_var = "PROOF100_TOKEN"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "proof100": {
      "type": "remote",
      "url": "https://proof.zketernity.app/mcp",
      "enabled": true,
      "headers": {
        "Authorization": "Bearer {env:PROOF100_TOKEN}"
      }
    }
  }
}
{
  "mcpServers": {
    "proof100": {
      "type": "http",
      "url": "https://proof.zketernity.app/mcp",
      "headers": {
        "Authorization": "Bearer ${PROOF100_TOKEN}"
      }
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=proof100&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vcHJvb2YuemtldGVybml0eS5hcHAvbWNwIiwiaGVhZGVycyI6eyJBdXRob3JpemF0aW9uIjoiQmVhcmVyICR7UFJPT0YxMDBfVE9LRU59In19"
}
{
  "servers": {
    "proof100": {
      "type": "http",
      "url": "https://proof.zketernity.app/mcp",
      "headers": {
        "Authorization": "Bearer ${PROOF100_TOKEN}"
      }
    }
  }
}
{
  "mcpServers": {
    "proof100": {
      "httpUrl": "https://proof.zketernity.app/mcp",
      "headers": {
        "Authorization": "Bearer ${PROOF100_TOKEN}"
      }
    }
  }
}
extensions:
  "proof100":
    enabled: true
    name: "proof100"
    type: streamable_http
    uri: "https://proof.zketernity.app/mcp"
    headers:
      "Authorization": "Bearer ${PROOF100_TOKEN}"
    timeout: 300

Placeholders to fill from your own secret store: ${PROOF100_TOKEN}. The registry never accepts secret values.

Quality 68 / 100needs work

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene71 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • pass
    tools.description_lengthdescriptions are concise
  • pass
    tools.schemasevery tool has an object input schema
  • fail
    tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
  • fail
    tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: timestamp_fingerprint (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); timestamp_text (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); check_balance (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)
  • pass
    tools.token_costabout 523 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stability50 · weight 15
  • pass
    stability.changes2 tool changes in 30 days
  • fail
    stability.rug_pull2 tools kept their name but changed most of their description in 30 days; review before trusting them
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

3 tools, about 523 tokens to load them all · tool set ba65efef2c8f · tools last changed 2026-10-29 · checked 2026-11-07 17:28 UTC

Tool changes

  • check_balancechangeddescriptionmeaning changed
    before

    Show how many Proof-100 proofs are left and the BTCZ deposit address for buying more.

    after · 36% of words in common

    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.

  • timestamp_fingerprintchangeddescription, input schemameaning changed
    before

    Write a SHA-256 fingerprint privately (shielded, zk-SNARKs) on the BitcoinZ blockchain. Returns the transaction ID and a viewing key for this one proof. Keep both: together they let anyone you choose verify this proof, and nothing else. Uses 1 Proof-100 proof.

    after · 25% of words in common

    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.

Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 97 / 100

provenance90
liveness99
freshness100
hygiene100

+repository +namespace-matches-repo +website +reachable +uptime-98% +updated-11d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://proof.zketernity.app/mcp streamable-httpapi_key ${PROOF100_TOKEN}yes98%460 ms2025-11-252026-11-07

Tools (3)

check_balanceShow 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.
timestamp_fingerprintCreate 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_textCompute 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.

Schemas: list_tools.

Similar MCP servers

More from io.github.ZKStamp

Official server.json
{
  "name": "io.github.ZKStamp/proof100",
  "title": "ZKStamp Proof-100",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://proof.zketernity.app/mcp",
      "type": "streamable-http",
      "headers": [
        {
          "name": "Authorization",
          "isSecret": true,
          "isRequired": true,
          "description": "Bearer followed by your Proof-100 account key (starts with p100_)"
        }
      ]
    }
  ],
  "version": "0.2.0",
  "repository": {
    "url": "https://github.com/ZKStamp/Proof100",
    "source": "github"
  },
  "websiteUrl": "https://proof.zketernity.app/llms.txt",
  "description": "Shielded proof-of-existence timestamps on BitcoinZ (zk-SNARKs). Free trial: 3 proofs."
}