Home / MCP registry index / com.advocatemcp/advocate
AdvocateMCP
com.advocatemcp/advocate in the official MCP registry.
Endpoint https://api.advocatemcp.com/mcp. Source: github.com/cameronjmcewan-dev/advocatemcp.
The registry describes it as: MCP layer for local businesses: discover, query, book, and transact with verified SMB AI agents.
We read its 18 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules.
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
search_businesses get_credentials get_cancellation_policy get_availability get_booking_destination list_services get_quote reserve_slot confirm_booking initiate_handoff request_callback subscribe_to_updates query_business_agent get_payment_handoff_url request_service submit_quote_request create_booking_payment_link cancel_booking
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-advocatemcp-advocate)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.