Home / MCP registry index / ai.surfingdog/inbox
Surfing Dog Inbox
ai.surfingdog/inbox in the official MCP registry.
Endpoint https://inbox.surfingdog.ai/mcp. Source: github.com/surfingdogai/inbox.
The registry describes it as: Message, ask for a quote or book a call with Surfing Dog, through its open-source inbox.
We read its 19 tools on 2026-10-21. 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
get_business_profile list_services list_products check_availability request_quote create_booking create_order get_item_status accept_offer decline_offer suggest_time make_offer provide_details withdraw_from_contract request_return cancel_item send_message acknowledge_receipt verify_customer
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-surfingdog-inbox)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.