Zambo

Zambo connects a compatible MCP client to a hosted work platform for external tasks, memory and session continuity. A client submits a job, the selected tools perform the work, and calls return verifiable AER-1 receipts. Its HANDOVER workflow packages a session so work can continue in another client with the relevant context and receipts carried across.

The skill describes a catalog of 153 tools, with 36 exposed on the default surface and additional capabilities reachable through capability_search and the full catalog. These counts can change. Read tool names and parameters from the runtime tools/list response rather than hardcoding a catalog. Suggested starting points include handover, capability_search, memory_remember, memory_recall and continuity_get_recent.

For work that will change hands, execute the needed steps first and then call handover with the goal, summary and work itself. The result is a link carrying the context and records for the receiver. A handover produces a receipt pair, one for wrapping up and one for pickup. This hosted workflow differs from memory-handoff, which moves context through a local handoff file within a project.

Use Zambo when an authorized task needs live data, code audits, security reviews, lead or market research, wallet or token analysis, or document work. It also fits a session that must continue in another client or a deliverable that needs a shareable record for later inspection. Pure questions and creative writing without external execution do not need the service.

Hosted execution, memory and shareable handovers must remain inside the user's intended task and data scope. Submit the context needed for that work, leaving unrelated session history, private information and secrets out by default. Calls can change state, write hosted memory, run audits or produce deliverables. Tool-call data is sent to the hosted service, and receipt records may include arguments. Share public receipts and handover links only within the intended sharing scope.

Begin with an authorized job, the context it actually needs and a remote-MCP-capable client. Describe the requested work in the tool call in ordinary task language. Outputs include the selected tool's result, a receipt identifier and, when handover is used, a link for continuing the session elsewhere. Report what the job was, which tools ran and the outcome together with the receipt.

Receipt verification checks that the saved record matches what was recorded and has not changed afterward. It does not establish that the underlying result is true or that the caller had authorization. If a response has no receipt, treat it as unrecorded and say so. A genuine unchanged record returns the verification outcome verified.

When a call fails, report the service error with enough detail for diagnosis while summarizing or redacting sensitive content that echoed request arguments or credentials. If usage reaches a limit, explain the available passes instead of failing silently.

The hosted MCP endpoint is compatible with remote-server clients including Claude, Cursor, Codex and Gemini. Network access is required, but no API key, signup or account is needed. One supplied connection command is:

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

After connecting, list tools before selecting names and parameters. Receipts follow AER-1, IETF draft-zambo-aer1-26. Verification is available through the public verification page or a GET request to the receipt verification endpoint with the receipt ID.

The described free tier allows 20 calls and one wrap-up daily; picking up in another client is always free. Optional passes include a $0.99 Day Pass for unlimited calls over 24 hours without renewal, and a Zambo Pass at $29 for 30 days or $290 for 365 days as single payments. $ZAMBO holders pay $19 for 30 days. Payment options include USDC on Base through x402 for automated clients and card or PayPal for people. The original skill is published under the MIT License in the zambo-skills repository.