Umbra Proof
io.github.beepboop2025Published by GitHub account beepboop2025v0.1.2Updated Oct 24, 2026
Verify Umbra bridge accountability proofs (signed receipts, checkpoints, Merkle inclusion).
The publisher's own server: Proof Holdings
Overview
Verifies Umbra bridge accountability proofs, including signed receipts, Merkle checkpoints, and inclusion proofs.
- What you can do
- This local MCP server checks the cryptographic evidence produced by the Umbra cross-chain bridge's Proof Layer. It verifies signed swap receipts (Ed25519 and ML-DSA-65), signed Merkle checkpoints, and RFC 6962 inclusion and consistency proofs, so an assistant can confirm that an order's history has not been altered. It is a verification tool, not a bridge client: it does not create orders or move funds.
- When to use it
- Use it when you need to independently check that an Umbra bridge order or audit entry is backed by valid signed receipts and transparency-log proofs, for example when auditing a swap or confirming that a checkpoint is an append-only extension of an earlier one.
- Requirements
- Runs as a local process on the user's machine via the published OCI image (ghcr.io/beepboop2025/umbra-proof-mcp:v0.1.2) over stdio. No authentication, environment variables, or headers are declared. Desktop only; not available as a web executable. It needs access to the proof data it verifies, such as receipts and checkpoints.
Installation
In SourceWeft
- Open Umbra Proof in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.2LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.
Other Proof integrations
Proof Holdings
holdings.proofOfficial publisher
Proof Holdings MCP server lets an assistant run identity and control verifications (phone, email, domain, wallet), manage proof tokens and delegations, and…
Proof of Work
Published by GitHub account kivtxs
Lets an assistant read the rules of Proof of Work, check for a local account, and create an agent account to post, vote and back claims.
QuietProof
Published by GitHub account frankjie3-create
QuietProof offers free discovery tools for a catalog of deterministic, read-only audits that are paid per call in USDC on Base via x402.
SCRIPTMASTERLABS — 402Proof
com.scriptmasterlabs
Remote MCP endpoint for creating, verifying and scoring invoices settled with RLUSD on the XRPL ledger, with self-proof of settlements.
ZKStamp Proof-100
Published by GitHub account ZKStamp
Remote MCP server that writes SHA-256 fingerprints to the BitcoinZ blockchain as shielded, dated proof-of-existence timestamps.