mcpField
U
umbra-proof

umbra-proof

Local
github.com/beepboop2025Security

About umbra-proof

umbra-proof provides ways to verify Umbra bridge receipts and transparency proofs without relying on the bridge operator. It is for users and independent observers who need to check signed order histories, Merkle inclusion and append-only checkpoints.

Key features

  1. 01Verify signed, hash-chained receipts
  2. 02Check Ed25519 and ML-DSA-65 signatures
  3. 03Verify Merkle inclusion proofs
  4. 04Check checkpoint consistency proofs
  5. 05Offline Python and browser verifiers

Use cases

  1. 01Validate a bridge order's receipt history
  2. 02Confirm an audit entry is in a checkpoint
  3. 03Check that transparency history only extends
  4. 04Verify proofs offline without network access

MCP support

The README does not describe MCP support.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"beepboop2025-umbra-proof": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/beepboop2025/umbra-proof-mcp:v0.1.2"
]
}
}
}
Run commanddocker run -i --rm ghcr.io/beepboop2025/umbra-proof-mcp:v0.1.2

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
ocighcr.io/beepboop2025/umbra-proof-mcp:v0.1.2

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.