Home / MCP registry index / io.usefulapi/agencyzoom
AgencyZoom MCP by usefulapi
io.usefulapi/agencyzoom in the official MCP registry.
Endpoint https://agencyzoom.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read leads, customers, policies and tasks; add notes, tasks and leads in AgencyZoom.
We read its 28 tools on 2026-11-06. 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 about every two weeks.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http agencyzoom https://agencyzoom.usefulapi.io/mcp{
"mcpServers": {
"agencyzoom": {
"url": "https://agencyzoom.usefulapi.io/mcp"
}
}
}code --add-mcp '{"name":"agencyzoom","type":"http","url":"https://agencyzoom.usefulapi.io/mcp"}'Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.
Let Claude Code check servers as it adds them
With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.
claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-pluginsTools it advertises
agencyzoom_search_leads agencyzoom_get_lead agencyzoom_get_lead_notes agencyzoom_get_lead_tasks agencyzoom_get_lead_opportunities agencyzoom_search_customers agencyzoom_get_customer agencyzoom_get_customer_policies agencyzoom_get_customer_tasks agencyzoom_search_tasks agencyzoom_get_task agencyzoom_search_service_tickets agencyzoom_get_sales_summary agencyzoom_list_pipelines agencyzoom_list_employees agencyzoom_list_lead_sources agencyzoom_list_carriers agencyzoom_list_product_lines agencyzoom_list_tags agencyzoom_list_service_ticket_options agencyzoom_create_lead agencyzoom_add_lead_note agencyzoom_add_customer_note agencyzoom_create_task agencyzoom_complete_task agencyzoom_reopen_task agencyzoom_move_lead_stage agencyzoom_create_service_ticket
Tool changes
We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.
Fingerprint of its tools at our last full read (2026-11-06):
d5716a1aaa5cd9c2. A client can hash the tools it is served the same way and compare;
the full value and a hash per tool are in this page as JSON.
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-agencyzoom)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. How tool poisoning works. What we found across the registry. Check another server.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.