# ZKStamp Proof-100 (remote · proof.zketernity.app)

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

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `proof.zketernity.app`: 69/100 (this document), [markdown](https://verifymcp.io/servers/zkstamp-proof100/proof.md), [page](https://verifymcp.io/servers/zkstamp-proof100/proof)

## Channel facts

- Endpoint: `https://proof.zketernity.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 461 tokens (~153/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the ZKStamp Proof-100 MCP server?

ZKStamp Proof-100 is a hosted endpoint at https://proof.zketernity.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http zkstamp-proof100 'https://proof.zketernity.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "zkstamp-proof100": {
      "url": "https://proof.zketernity.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "zkstamp-proof100": {
      "type": "http",
      "url": "https://proof.zketernity.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.zkstamp-proof100]
url = "https://proof.zketernity.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "zkstamp-proof100": {
      "type": "remote",
      "url": "https://proof.zketernity.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add zkstamp-proof100 --url 'https://proof.zketernity.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  zkstamp-proof100:
    url: "https://proof.zketernity.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "zkstamp-proof100": {
      "Transport": "http",
      "Url": "https://proof.zketernity.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add zkstamp-proof100 -t streamable-http -u 'https://proof.zketernity.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "zkstamp-proof100": {
      "type": "http",
      "url": "https://proof.zketernity.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 66, 0)

- [security] Tool “check_balance” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail

### 2026-10-28 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-27 (score 65)

First indexed and scored.

## MCP tools (3)

### `timestamp_fingerprint` (~279 tokens)

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.

Input parameters:

- `fingerprint` (string, required): SHA-256 hash of the file, as 64 hexadecimal characters (case-insensitive), e.g. 968c796b7f8c9259ee92d7168d882df2f347d9711a51da90182c98d69139cdb7

### `timestamp_text` (~90 tokens)

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.

Input parameters:

- `text` (string, required): The exact text to timestamp

### `check_balance` (~92 tokens)

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/zkstamp-proof100/proof#diagnostics

## Score history

- 2026-11-05: 69
- 2026-11-04: 68
- 2026-11-03: 68
- 2026-11-02: 67
- 2026-11-01: 67
- 2026-10-31: 66
- 2026-10-30: 66
- 2026-10-29: 66
- 2026-10-28: 66
- 2026-10-27: 65

## Common questions

### What is the ZKStamp Proof-100 MCP server?

ZKStamp Proof-100 is an MCP server listed in the public MCP registry as io.github.ZKStamp/proof100. Shielded proof-of-existence timestamps on BitcoinZ (zk-SNARKs). Free trial: 3 proofs. This page covers its hosted endpoint (https://proof.zketernity.app/mcp).

### Is the ZKStamp Proof-100 MCP server safe to use?

ZKStamp Proof-100 scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the ZKStamp Proof-100 MCP server expose?

ZKStamp Proof-100 exposes 3 tools: timestamp_fingerprint, timestamp_text, check_balance. Their descriptions and schemas cost roughly 461 tokens of context every time the server is loaded.

### Does the ZKStamp Proof-100 MCP server require authentication?

No. We connected to ZKStamp Proof-100 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ZKStamp Proof-100 MCP server still maintained?

ZKStamp Proof-100 is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://proof.zketernity.app/mcp
- Authorisation metadata: https://proof.zketernity.app/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/ZKStamp/Proof100
- Website: https://proof.zketernity.app/llms.txt
- Changelog RSS feed: https://verifymcp.io/servers/zkstamp-proof100/proof.xml
- Changelog JSON feed: https://verifymcp.io/servers/zkstamp-proof100/proof.json
- HTML version of this page: https://verifymcp.io/servers/zkstamp-proof100/proof