Add Zambo to Your AI. Switch Models. Keep the Receipts.

Agents do work.

Then somebody asks what happened, and we hand them a chat transcript.

"Done" is not a receipt. A plan is not execution. A confident answer is not evidence.

That's the gap I'm building Zambo around.

One hosted MCP connection. A record of what Zambo recorded. A link you can inspect instead of asking the model to tell the story again.

What a Receipt Is

A Zambo receipt records the tool call, its status, and committed result bytes. You can retrieve the record and check whether the bytes match the published hash.

That makes changes detectable against the commitment. It does not make the answer true. It does not independently authenticate the issuer. And it does not prove an outside action happened unless there's corresponding evidence of that action.

Wrong result? You can have an intact receipt of a wrong result.

Failed call? That's a failed call, not completed work.

That's the point. Keep the claim smaller than the evidence.

The Connection

This is the address:

https://zambo.dev/mcp

No Zambo signup or API key to start. No OAuth for the anonymous endpoint.

Your AI platform can still require its own account, plan, permissions, or API key. Free Zambo does not mean free model usage.

Claude Desktop and Claude.ai

Use the native remote connector. You don't need a local bridge for the free connection.

  1. Open Customize > Connectors.
  2. Choose + Add > Add custom connector.
  3. Name it zambo.
  4. Paste https://zambo.dev/mcp and continue.
  5. Choose no sign-in if the dialog asks.
  6. In a chat, use + > Connectors to enable Zambo for that conversation.

ChatGPT

  1. On ChatGPT web, go to Plugins.
  2. Select + > Add custom MCP server.
  3. Name it zambo.
  4. Use https://zambo.dev/mcp as the server URL.
  5. Choose no authentication.
  6. Create as a plugin, then install it.

Cursor

Create or edit .cursor/mcp.json:

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

VS Code / Copilot

Create .vscode/mcp.json:

{ "servers": { "zambo": { "type": "http", "url": "https://zambo.dev/mcp" } } }

Note servers, not mcpServers.

Claude Code 

claude mcp add --transport http --scope user zambo https://zambo.dev/mcp

Connected? Do This First

Ask your AI:

Use the Zambo MCP server. Call new_session with no arguments. Save the returned session_id. Use that exact value as _session_id on related Zambo calls. Return the receipt link and the recorded status, not just "done".

Switch AIs. Keep the Receipts.

Keep the same _session_id for the same job. Connect Zambo to the second AI with the same endpoint. Give it the session ID and tell it to inspect the trail before continuing.

Same job ID. Same Zambo trail. Different host AI.

That's the Whole Loop

Connect. Run. Inspect. Keep the link.

Zambo is the hosted implementation. AER-1 is the open draft spec for the receipt format. Not an adopted IETF standard. Not proof that an AI can never be wrong.

Just a smaller gap between "the agent said it did" and a record you can actually check.

Try it now, no install: https://zambo.dev/demo/

Verify any receipt: https://zambo.dev/verify/

The spec: https://datatracker.ietf.org/doc/draft-zambo-aer1/

Your AI said "done." For $0.99, prove it: https://zambo.dev/day-pass/