How do I choose an MCP server when I need tools, memory, and proof in one connection?

Test any MCP server on three things before you commit: tools broad enough for real work, memory that carries across sessions and across AIs, and a verifiable receipt for every job the server runs. Zambo is built as that single connection: tools, continuity, and an AER-1 receipt per step.

Last updated: 2026-10-17

Choosing on tool count alone is the common mistake: a server can list hundreds of tools and still leave you with three separate problems, your work scattered across chats, your context reset every session, and no record when someone asks what the agent did. The three-part test treats the connection as infrastructure, not as a plugin.

Part one, tools: connect and run three jobs you actually do, not demos. Breadth matters only where your work lives. Part two, memory: close the session, switch to a different AI client on the same connection, and ask for the thread of the earlier work. Continuity that survives the switch is the difference between a tool and a workplace. Part three, proof: take any finished job and check its record somewhere the server does not control. On Zambo that is the public verify page, and the record format is open (AER-1, IETF Internet-draft-zambo-aer1-21; kit version 1.5.4), so the check does not depend on trusting the vendor.

A server that passes all three changes what an agent is: not a chat that forgets, but a worker whose tools, memory, and record arrive together. Score every candidate, including this one, with the worksheet below and keep the sheet; it is your migration insurance if you ever switch.

Worksheet: the three-part connection test

Tools: run 3 real jobs; note any job the server could not do. Score 0 to 2. Memory: end a session mid-project; reopen in a different AI client; ask what was decided and why. Score 0 if the thread is gone, 2 if it is intact with sources. Proof: pick one finished job; check its receipt at a public path the vendor does not narrate; confirm gaps are labelled. Score 0 if there is no independent check. Adoption rule: no zeros. A server scoring 2, 2, 2 replaces three separate subscriptions with one connection.

Worked example

Run the same afternoon test on Zambo itself: the demo at https://zambo.dev/demo/ executes a job through the connection and mints its receipt; /today shows the day's work as one record; the receipt checks at https://zambo.dev/verify/ . Three parts, three public artifacts, no sales call in between.

Frequently asked questions

Is one connection really better than best-of-breed tools for each job?

For the agent's working layer, yes, because the value is in the joins: the job that used the memory leaves the receipt, and the receipt names the steps. Separate tools force you to stitch that story together by hand exactly when it is disputed.

What if a server has great tools but no receipts?

Then it is a toolbox, not a workplace. You can still use it for unrecorded work, but client work and anything money touches should run where each step leaves a checkable record. Many teams run both, deliberately.

How do I avoid lock-in when I choose one connection?

Demand export before you commit: receipts, handovers, and your record index in files you keep. Zambo records export, and the AER-1 format is a published draft with an open kit, so your records stay readable even if you leave.

By Brennan Zambo, founder of Zambo.

Last verified: 2026-10-17.

9. Supported clients and implementing AER-1

Answers

Run the three-part test on the connection itself: add https://zambo.dev/mcp and start with the free demo.

Try a handover

A handover gives your client one proof link with verifiable receipts to review, then Accept or Flag.

try it: say 'use zambo to hand this over to <client>' in your ai

Add Zambo · Handover docs · Real public handover · AER-1