FORUM Merkle proof
get_proofReturn the Merkle audit path that ties one FORUM trust record to the daily release root: leaf, index (0-based leaf position), path (sibling hashes, leaf level first) and root. Same object as GET /v1/trust/{registry_name}/proof on the FORUM HTTP API. Verification recipe: (1) h = the 32 bytes of leaf (hex-decoded; leaf is the record's content_sha256), i = index. (2) For each hex sibling s in path, in order: if i is even, h = sha256(h + s_bytes); if i is odd, h = sha256(s_bytes + h); then i = i // 2. (3) hex(h) must equal root. Then compare root with merkle_root from get_method and with the on-chain anchor (method doc section 10.2); a root taken only from this response shows internal consistency, not publication. A valid proof shows that the record is part of the published release; it says nothing about whether the scored server is safe. A score is: Not a security guarantee, not a penetration test, not certification of code correctness. An unknown name returns isError with error=not_in_registry. Read-only.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"registry_name": "<registry_name>"
},
"name": "get_proof"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| registry_name | Yes | MCP Registry server name, exactly as the registry spells it: owner/name, e.g. io.github.pipeworx-io/19hz. Contains a slash; pass it raw (no URL-encoding). Case-sensitive. |