mcpbeat

Proof MCP Server

dev.tatastu/proof
not responding

Proof is listed as active in the registry but did not answer our last check. Last commit 20 Jul 2026.

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

Uptime history 40 hours of history · worst hour 0%
40 hours agonow
0.0%
Uptime 24h
0 of 91 checks
—
Tools
hidden behind auth
415 ms
Response time
average over 24h
0
Stars
last commit 20 Jul 2026

Connect this server

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

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"
    }
  }
}

Endpoints

URLTransportStateLatencyChecked
https://proof.tatastu.dev/mcp streamable-http answering 415 ms 13 min ago

Proof — questions

Answers built from our own checks of this server.

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 415 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. 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.