Skip to main content
Glama
ResultBond Verifier MCP Server

ResultBond Verifier MCP Server

Official
by valtris

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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      MCP server for offline verification of signed artifacts — receipts, manifests, and audit bundles. MIT licensed, works without accounts or API calls. Tools: self_test, verify_receipt, verify_bundle, explain_artifact.
      4
      6
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP hosts to verify agent spending mandates and receipts, providing stateless tools for authorization, chain verification, credential verification, and DID resolution.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Issue and verify signed receipts for agent actions, enabling durable, independently checkable proof of policy decisions. Supports offline verification via get_keyset and verify_receipt tools without an account.
      0
      Inno Setup
    • A
      license
      A
      quality
      B
      maintenance
      Enables agents to locally validate and decode transparency-log receipts against a chosen trust root, checking exact payload inclusion, grant admission, and receipt contents without a backend, account, key, or network. It also reports sealing, split-view, append-authority, and attribution outcomes using read-only tools.
      3
      167 npm
      MIT