ResultBond Verifier MCP Server
Officialby valtris
README.md
# ResultBond Verifier — public-client staging
**Read-only cryptographic verifier** for signed ResultBond Proof Receipts.
Not the ResultBond Judge: this package has no evaluator, signing, Linux runner,
hidden tests, escrow, GitHub API or hosted service.
## Installation
Python 3.12+ after the first verified PyPI release:
python -m pip install "resultbond-verifier[mcp]"
From a trusted local checkout for development:
python3.12 -m venv .venv
.venv/bin/python -m pip install -e ".[mcp]"
Check a locally saved receipt and a root-signed keyset:
resultbond-verify receipt.json --keyset resultbond-keys.json --min-serial 3
Exit code 0 means a trusted signed outcome (it may be FAIL or INCONCLUSIVE),
1 = signature valid but signer untrusted, 2 = invalid or unreadable evidence.
Only the JSON field **certified_pass** indicates a trusted PASS.
For MCP clients, start the installed command as a local stdio subprocess:
{
"mcpServers": {
"resultbond": {
"command": "/absolute/path/to/resultbond-verifier-mcp"
}
}
}
Tools: verify_receipt_tool(receipt_json, keyset_json?, minimum_keyset_serial=1),
and resultbond_capabilities(). Neither can alter files or make network calls.
The offline root public key is built in. A trusted outcome requires a valid
receipt signature, valid root-signed keyset, evaluator role and identity match,
time validity, no revocation and a serial >= the caller's trusted minimum.
The verifier cannot know the highest serial or independently confirm a
real-world result. Keep your highest observed serial in trusted storage.
Demo receipts with known public demo signing keys never certify PASS.
**License:** Apache-2.0 applies to this standalone verifier package only.
Private ResultBond Core and the Linux evaluator are not included or licensed
under Apache-2.0. Publication requires successful CI, audited wheel and
trusted publisher identity; no hosted MCP endpoint is enabled.
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues