Home / MCP registry index / com.buzzmebro/buzzmebro
BuzzMeBro
com.buzzmebro/buzzmebro in the official MCP registry.
Endpoint https://buzzmebro.com/api/mcp.
The registry describes it as: More than one roommate on your apartment buzzer number; settings decide who rings. Canada.
We read its 20 tools on 2026-10-26. 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
check_building create_setup send_phone_code confirm_phone_code start_checkout get_setup_status partner_program_info partner_apply partner_send_code partner_confirm_code partner_terms_link partner_claim_key partner_get_links partner_get_kit partner_get_stats partner_payout_link partner_list_sublinks partner_create_sublink partner_disable_sublink partner_rotate_key
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-buzzmebro-buzzmebro)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.