Zambo guide
MCP Security Checklist
Before you connect an MCP server, check who runs it, what it can see and whether it leaves receipts; here is the ten-line checklist.
Add Zambo to your AIThe ten checks
Check the record's format and commitment separately from the result itself. Use the verifier for the saved data, then inspect the underlying source and work.
Red flags
A receipt can show the saved record and its status. It does not prove that the result is correct, complete, lawful or accepted by the recipient. Compare the record with the original request and the result you received.
For a missing event, absence of a receipt is not proof that the action never happened. It only means that this record set does not show it.
Why receipts are a security feature
Each recorded call can be opened as its own receipt. The receipt lets a reader inspect the captured tool name, status, time and output commitment that are available on that record. Failed and rejected calls should remain visible as their actual status.
Use the receipt checker to compare the saved receipt data. That comparison checks the record, not the truth of a claim inside it.
Try this prompt
Start with a small request. Change the details to match your task.
Use Zambo to help with MCP security checklist. Show the steps you actually ran and give me a link I can review.
FAQ
What is MCP security checklist?
Before you connect an MCP server, check who runs it, what it can see and whether it leaves receipts; here is the ten-line checklist.
What does a Zambo receipt show?
It shows the saved record and its available status. It does not prove that the output is correct or complete.
How do I try this with Zambo?
Add Zambo to a supported AI app from /add, ask it to use Zambo for the task, then open the returned receipt link.
Try it with your AI
Connect Zambo once, then ask your AI to use it for a real task.
Add Zambo to your AI Try Zambo Chat