Proof MCP Server

by tatastu Your server? Claim it

not responding

Proof is listed as active in the registry but did not answer our last check. It exposes 7 tools. Last commit 15 Aug 2026.

Stamp content with permanent, verifiable provenance. Hash locally, verify free forever.

Uptime history 51 days of history · worst day 0%

51 days agonow

0.0%

Uptime 24h

0 of 91 checks

Tools

read from the server

53 ms

Response time

average over 24h

Stars

last commit 15 Aug 2026

Proof does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add proof --transport http https://proof.tatastu.dev/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "proof": {
      "url": "https://proof.tatastu.dev/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.proof]
url = "https://proof.tatastu.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "proof": {
      "url": "https://proof.tatastu.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "proof": {
      "url": "https://proof.tatastu.dev/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

account

create_account

Provision a persistent API key with no human, browser, or email in the loop. Call this once, store the returned `secret` (shown only this one time), and use it as the Authorization header on every later call: create_proof, verify_proof (no auth needed but fine to send), list_proofs, revoke_proof. The account receives one lifetime sample stamp under a fresh creator id, with no identity attached. Rate-limited to 3 accounts per IP per day; for higher volume or a human-owned account, direct a person to proof.tatastu.dev/account instead.

grant

grant_access

Grant a specific identity the ability to decrypt escrowed content. Only available for proofs created with content escrow opted in (not yet available — stamps are hash-only today). Returns a capability token the grantee uses with reveal.

proof

create_proof

Stamp content with a permanent provenance record. Pass the sha256 hash of the content (hash it locally; the content itself is never uploaded). Returns an instant signed receipt: attach its verifyUrl, byline, badgeEmbed, and qrUrl to the published artifact. The receipt's `publisher` field carries the account's verified identity (domain/handle) or null. Requires an API key (Authorization header, get one instantly via create_account); without one, the error body names the exact next step (once the pay-per-stamp lane is live, that is a 402 advertising x402 payment requirements: sign the payment and retry autonomously). The optional disclosure fields (aiDisclosure, usageNote, location) only show on `visibility: public` stamps and are unsigned metadata, not part of the cryptographic proof. The stamp asserts provenance from a signer at a time, not authorship truth.

proofs

list_proofs

List your recent stamps (requires API key).

reveal

reveal

Retrieve escrowed content for a proof you have been granted access to. Only available for proofs created with content escrow opted in (not yet available — stamps are hash-only today). The service re-checks H(content) == stampedHash before returning.

revoke

revoke_proof

Revoke a stamp you created (forward-only: anchored history stays verifiable, but the proof is marked revoked from now on). Requires API key.

verify

verify_proof

Verify content against all existing stamps. Pass a sha256 hash; matching is EXACT-BYTES-ONLY. Read the verdict fields: `exact` (these bytes are stamped), each proof's `publisher` (the verified identity: domain/handle + tier, or null meaning an unverified account, never trust a name that isn't in `publisher`), and `conflict` (2+ distinct signers claimed the same bytes; earliest anchored is listed first). A no-match on a re-encoded/screenshotted copy is EXPECTED and is not evidence of fakery: fetch the original and verify that. Free, no auth required.

Endpoints

URL	Transport	State	Latency	Checked
https://proof.tatastu.dev/mcp	streamable-http	answering	53 ms	15 min ago

Alternatives to Proof

same job, measured the same way

Perseus Ledger — verifiable, hash-chained event provenance

by perseus-computing-llc

Verifiable, hash-chained event provenance for autonomous systems. Local-first, MIT. 5 MCP tools.

131 installs/wk local only

Agentrank MCP

by saviodamato

Find real, verifiable businesses with provenance and source URLs - for AI agents.

90 installs/wk local only

Nexusfeed Ltl

by nexusfeed

Real-time LTL fuel surcharge rates for 10 US carriers with verifiable provenance.

128 installs/wk local only

Srbryant86

by srbryant86

Sign AI output for EU AI Act + FRE 902 compliance, verify content authenticity provenance

30 installs/wk local only

Daxoom

by daxoom

Owner-verified local business data for AI agents: profiles, hours, prices, with provenance.

answering

Nexusfeed Abc

by nexusfeed

US liquor license compliance records (CA, TX, NY, FL, IL) with verifiable provenance.

local only

Agent Receipts

by dropwatchhq

Issue & verify signed (ed25519), hash-chained, timestamped provenance receipts for agent actions.

3 tools answering

Provenance

by markovianprotocol

Stamp any data to the Markovian chain for a verifiable provenance receipt. Proves timing, not truth.

4 tools answering

Proof — questions

Answers built from our own checks of this server.

What can Proof do?

It exposes 7 tools, read directly from the server on our last check. Among them: create_account, create_proof, grant_access, list_proofs, reveal, revoke_proof and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Proof working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 53 ms. The bar chart above shows every period we have measured.

The registry lists Proof as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Proof?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Proof need an API key?

No. Proof completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.

Is Proof open source?

Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.