Umbra Proof runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 16 Aug 2026.
Verify Umbra bridge accountability proofs (signed receipts, checkpoints, Merkle inclusion).
What the code does
We read the source, 22 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
<script src="https://telegram.org/js/telegram-web-app.js"></script>
out.innerHTML = verdict(allOk,
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Umbra Proof
same job, measured the same wayFind governed AI capabilities and verify signed receipts. Read-only, no account.
Branch-scoped runbooks, remote checkpoints, and auditable verification receipts.
Issue signed receipts for AI agent actions; verify any receipt offline - free, no account.
Read crypto reference prices and verify signed receipts. Includes limited keyless samples.
Verify an AI agent's payment authority: signed mandates, allowlists, and tamper-proof receipts.
Verify UK businesses (FSA/CQC) + signed attestations, mandates & receipts for AI agents.
Contract-change authorization for AI agents. Signed receipts verify offline.
Verify AI-agent revenue: recompute a Merkle proof and check it against an on-chain anchor.
Umbra Proof — questions
Answers built from our own checks of this server.