Home / MCP registry index / io.github.zambodotdev/zambo
Zambo
io.github.zambodotdev/zambo in the official MCP registry.
Endpoint https://zambo.dev/api/mcp. Source: github.com/zambodotdev/zambo-mcp.
The registry describes it as: Give your AI hands. One URL. Type a job. Get a receipt.
We read its 35 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
day_pass_redeem memory_remember memory_recall spend_limit_set spend_limit_status handover_accept handover handover_status handover_list zambo_home activity_today workflow_close workflow_seal zambo_universal new_session continuity_get_recent continuity_list_threads continuity_open_thread continuity_start_thread continuity_set_prefs journal_log live_price pdf_extract leadsignal provibe_audit ghost_audit_site ghost_audit_status ghost_audit_report credithunt prompt_shield day_pass_checkout_link day_pass_activate day_pass_status pass_status capability_search
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-zambodotdev-zambo)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.