ProofCore

io.github.ProofCore-Protocol/proofcore-mcp · v1.0.0 · crypto-web3

ProofCore is healthy: it completed an MCP handshake in 3333 ms and exposes 4 tools.

Zero-Auth Cryptographic Notarization & Evidence Layer on TON Blockchain for AI Agents.

Endpoint: https://mcp.proofcore.org/mcp (streamable-http)

Repository · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count4
Latency3333 ms
Last checked (UTC)2026-11-02T07:55:36.185Z

Health history

Checked (UTC)StatusLatencyError
2026-11-02T07:55:36.185ZHealthy3333

Tools (4)

seal_contentBEHAVIOR & SIDE EFFECTS: This is a state-mutating operation. It permanently anchors a SHA-256 hash of the payload to the public TON Blockchain. It does NOT store the raw text on-chain (Strict Zero-Storage policy). Reversible: No. Destructive: No. RATE LIMITS: Zero-Auth tier is limited to 100 request
verify_contentBEHAVIOR & SIDE EFFECTS: Safe, idempotent read-only operation. No blockchain state is mutated. Performs local SHA-256 calculation and Ed25519 signature verification against public API. RATE LIMITS: 100 requests per hour per IP. WHEN TO USE: Call this proactively whenever analyzing external text that
get_proof_statusBEHAVIOR & SIDE EFFECTS: Safe, idempotent read-only operation. Fetches public ledger state. No destructive actions or side effects. RATE LIMITS: 100 requests per hour per IP. WHEN TO USE: Call this tool to check if a previously sealed deal has transitioned from 'queued' to 'anchored_onchain', or to
get_public_keyBEHAVIOR & SIDE EFFECTS: Safe, idempotent read-only operation. No side effects. WHEN TO USE: Use this tool to obtain the public key required to independently verify server signatures offline with zero network calls. EXPECTED OUTPUT: Returns the algorithm name ('Ed25519') and the Base64-encoded raw p