Your server.json
Drop a server.json file or click to choose one, or just paste below.
The worked example: Zambo's own record
The button above loads the server entry Zambo actually publishes in the official MCP registry, read live from registry.modelcontextprotocol.io on 2026-10-25. Its registry name is dev.zambo/zambo, version 4.1.0, with one remote of type streamable-http at https://zambo.dev/mcp. Run the validator on it and every required field passes: this is the shape to copy.
A valid server.json is step one; Zambo also issues a verifiable receipt for every call the server makes, so the work your server does can be checked afterwards, not just listed. The short route in is zambo.dev/add. Connect any MCP client to zambo.dev/mcp with no key: 20 free calls per day, then a Day Pass at $0.99 USDC on Base for 24h or a Zambo Pass at $29 for 30 days. Zambo is the verifiable work layer for AI, and its flagship product is HANDOVER. An agent receipt is a record of one ai agent tool call that anyone can check: it keeps the exact saved bytes and their sha-256 digest, and it proves the result was not changed since it was saved, not that it was right.
Keep reading
- AER-1: the verifiable execution receipt for AI agents, the flagship format page
- Verify a Zambo receipt
- Answers: plain-language answers to agent work questions
- The AER-1 conformance corpus, the published test vectors
- Seal a deliverable, the companion free tool: fingerprint a file in your browser
- Run the AER-1 conformance test in your browser
- MCP server compliance checklist: audit records for SOC 2 and the EU AI Act