Add receipts to OpenHands: check the run, not the report

Add the server: Agent Canvas, CLI, or SDK

OpenHands takes MCP servers on every surface it ships, and Zambo is a hosted Streamable HTTP endpoint, so there is nothing to install locally:

Agent Canvas (local or connected to OpenHands Cloud): open Customize, then MCP Servers, then Add custom server. Set Server Type to SHTTP, the transport OpenHands recommends for remote servers, URL to https://zambo.dev/mcp, and Authentication to None. Click Test connection, a working server reports how many tools it provides, then Save.

CLI: one command writes the same entry into ~/.openhands/mcp.json:

openhands mcp add zambo --transport http https://zambo.dev/mcp

SDK: pass the config to your agent:

mcp_config = {
    "mcpServers": {
        "zambo": {"url": "https://zambo.dev/mcp"}
    }
}

agent = Agent(..., mcp_config=mcp_config)

One rule from the OpenHands docs worth knowing before you test: servers you add or change apply to new conversations, not to conversations already running. Add the server, then start a fresh conversation, and the agent can call Zambo's tools alongside its built-in ones. The endpoint serves 153 tools in total, 36 of them on the default surface the client sees first.

What gets receipted, and what does not

Calls served through the endpoint return a receipt inside the response itself, with a public URL at https://zambo.dev/run/ that anyone can open. Route the steps a reviewer will ask about through it: the research the fix was based on, the checks run against the result, the decisions recorded along the way, and the wrap-up that hands the finished job over with its record attached.

The honest edge: OpenHands' own built-in actions, the file edits, terminal commands, and browser steps it runs itself, are not receipted by this route. No page should tell you a tool-call record covers work that never passed through the tool. What the endpoint route gives you is a checkable record of the working calls you route through it, kept outside the run, in a form that survives the session, the workspace, and the agent's own summary of itself.

Verify one yourself before you rely on it

Take any receipt from your first run and check it at zambo.dev/verify. The verifier recomputes the commitment from the saved bytes and compares it with the commitment fixed when the call ran. A match means the saved record is the record made at execution. Then do the negative test every evidence system should survive: change one character in a copy of the record and check again. It fails, plainly, in public. A record system that cannot fail in public cannot pass in a way that means anything.

And keep the claim honest when you present it: a receipt proves the saved call record was not changed after it was saved. It does not prove the code the agent wrote was good. Review still matters; the receipt just makes the review about the real calls instead of about a summary of them.

Questions, answered