Labsco
MCP SERVER

TinyZKP

by logannye ↗

Mint a tamper-evident proof that a chain of steps really ran as claimed — start at X, apply these steps, provably reach Y — and hand over the receipt instead of your word.

Identity, Access, Secrets & Encryption
Summary
A verifiable receipt instead of "trust me".

When an agent says a sequence of steps happened, this turns the claim into a proof someone else can check in milliseconds without re-running any of it.

What it is

A public MCP endpoint for TinyZKP, a proof service for state transitions. An agent picks a template, submits the run, and gets back a proof that anyone can verify in milliseconds without re-running the work.

What you get
  • list_templates and describe_template show the state-transition shapes on offer and what each one expects
  • prove_template submits a run for proving; poll_job reports on it while it works
  • get_proof returns the finished proof; verify_proof checks one you have been handed
  • The endpoint is public and rate-limited by a server-side concurrency cap, so a client can call it before any account exists
  • SDKs for TypeScript and Python, the @tinyzkp/cli command line client, and a WASM verifier for checking a proof in the browser
Requirements

Nothing to install for the MCP path: point an MCP client at `https://mcp.tinyzkp.com` over HTTP, with no signup, API key or card. An account only matters past the free tier of 100 proofs a month.

Setup effort

One command — hc-mcp-stdio