Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

BuzzMeBro

REMOTE · BUZZMEBRO.COM

More than one roommate on your apartment buzzer number; settings decide who rings. Canada.

Available components

70 Trust /100

Last scanned (7 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 18 Oct 2026.

Category IoT and Hardware

Recent critical change

Authorization (14 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security66
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2780 tokens (~139/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “partner_disable_sublink”, which the server declares destructive security
    • Tool “partner_get_kit” rewrote its description, which is the text the model reads security
    • Schema quality: 2388 → 2780 ▼ functional
    • Server version: 1.1.0 → 1.2.0 functional
    • New tool “partner_create_sublink” functional
    • New tool “partner_list_sublinks” functional
    • “partner_apply” added an optional parameter “payouts_off” cosmetic
    • “partner_apply” reworded the description of “persona” cosmetic
  • 14 Oct 26 −6
    • Authorization: partial → fail ▼ critical
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “partner_rotate_key”, which the server declares destructive security
    • Schema quality: 189 → 140 ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • New tool “partner_apply” functional
    • New tool “partner_claim_key” functional
    • New tool “partner_confirm_code” functional
    • New tool “partner_get_kit” functional
    • New tool “partner_get_links” functional
    • New tool “partner_get_stats” functional
    • New tool “partner_payout_link” functional
    • New tool “partner_program_info” functional
    • New tool “partner_send_code” functional
    • New tool “partner_terms_link” functional
  • 13 Oct 26 74

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 18 Oct 2026 · Probed https://buzzmebro.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=buzzmebro.com CN=YR2,O=Let's Encrypt,C=US 7 Oct 2026 5 Jan 2027 RSA 2048 SHA256-RSA 68fcb56f0f14d3fd59f8f0091081a014394
SANs: buzzmebro.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of buzzmebro.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
buzzmebro.com. present 2371 13 Verified
buzzmebro.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'nonce-v6OaWPqS2D1kq1ubAkKf7g==' 'strict-dynamic' https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self' data:; connect-src 'self' https://challenges.cloudflare.com https://o4511861855420416.ingest.us.sentry.io https://us.i.posthog.com https://qaaehpfxbfarbmdphihr.supabase.co wss://qaaehpfxbfarbmdphihr.supabase.co; frame-src 'self' https://challenges.cloudflare.com; worker-src 'self' blob:; manifest-src 'self'; media-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), browsing-topics=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://buzzmebro.com/api/mcp Verified 200
http (plaintext) http://buzzmebro.com/api/mcp HTTPS enforced 308 https://buzzmebro.com/api/mcp
MCP tools · 20 exposed · ~2,140 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_building ~83

Checks whether BuzzMeBro can give this building a local buzzer number, and returns the price, the free-trial terms and how the service works. Call this first. Stores nothing and costs nothing.

NameTypeReqDescription
postal_codestringyesThe apartment building’s postal code, e.g. "M4B 1B3". Canadian postal codes only for now.

No output schema declared.

No examples provided.

confirm_phone_code ~99

Checks the code the person read back to you. This proves the phone is theirs, which matters because that phone will open their front door. Five tries per setup. Next: start_checkout.

NameTypeReqDescription
codestringyesThe digits from the BuzzMeBro text, e.g. "482913".
setup_idstringyessetup_id from create_setup.
status_tokenstringyesstatus_token from create_setup. Keep it private.

No output schema declared.

No examples provided.

create_setup ~244

Creates a BuzzMeBro setup for the person and returns setup_id and a status_token you must keep for every later call (plus setup_url, a fallback link if you cannot relay a texted code). Only call it after check_building said available and the person has asked you to set it up. No text message is sent and nothing is charged by this call. Next: send_phone_code.

NameTypeReqDescription
agent_namestring–Optional: your name as the person knows you (e.g. "ChatGPT", "Claude"), shown on their link page.
mobile_phonestringyesThe person’s own mobile number. It becomes the first phone the buzzer rings and how they sign in; we text it a code when they open the link.
postal_codestringyesThe apartment building’s postal code, e.g. "M4B 1B3". Canadian postal codes only for now.
referral_codestring–Optional BuzzMeBro referral code from a friend.
unitstringyesTheir apartment or unit number as the lobby panel lists it, e.g. "1502", "B" or "PH3".

No output schema declared.

No examples provided.

get_setup_status ~122

Reads how far the setup has got and says what to do next. Once the person has paid, this call gets their number; when status is "ready" it returns their new BuzzMeBro number and swap_the_buzzer: the steps to get the building to point the buzzer at that number, and ready-to-send messages for building management, the landlord, the concierge, the superintendent or a building portal.

NameTypeReqDescription
setup_idstringyessetup_id from create_setup.
status_tokenstringyesstatus_token from create_setup. Keep it private.

No output schema declared.

No examples provided.

partner_apply ~221

Starts a partner application with the person’s details and returns application_id and application_token. Only call it when the person has asked to join. No text is sent by this call. Next: partner_send_code.

NameTypeReqDescription
buildingstring–Optional: the building or company they work with.
emailstringyesThe person’s email.
employer_okboolean–If they work for a building or concierge company: has their employer allowed it?
mobile_phonestringyesThe person’s own Canadian mobile number. We text it a code.
namestringyesThe person’s name.
payouts_offboolean–Optional: true for organisations that cannot take money (for example a university or a settlement agency). Their residents still get the perk; no payouts are ever made.
personastringyesThe partner type: how they meet renters (front desk or building staff, leasing agent, mover, tenant insurance, co-living, university, telecom, listing site, relocation, landlord, move-in service, del…

No output schema declared.

No examples provided.

partner_claim_key ~91

After the person accepted the terms: returns their partner link, code and partner key. The key is shown once; keep it private and use it for the partner_get_* tools. The application token stops working after this call.

NameTypeReqDescription
application_idstringyesapplication_id from partner_apply.
application_tokenstringyesapplication_token from partner_apply. Keep it private; it collects the partner key once.

No output schema declared.

No examples provided.

partner_confirm_code ~75

Checks the texted code. Five tries per application. Next: partner_terms_link.

NameTypeReqDescription
application_idstringyesapplication_id from partner_apply.
application_tokenstringyesapplication_token from partner_apply. Keep it private; it collects the partner key once.
codestringyesThe digits from the text.

No output schema declared.

No examples provided.

partner_create_sublink ~102

Adds a tracked link with its own code for one location, building or staff member (up to 50). Renters who use it count for this partner, with the same two-months-free perk.

NameTypeReqDescription
labelstringyesA name for the link, e.g. "King St location".
partner_keystring–The partner key from partner_claim_key. On REST send it as "Authorization: Bearer <key>" instead.

No output schema declared.

No examples provided.

partner_disable_sublink ~80

Switches off one tracked link: its code stops bringing new apartments. Apartments it already brought stay with the partner.

NameTypeReqDescription
partner_keystring–The partner key from partner_claim_key. On REST send it as "Authorization: Bearer <key>" instead.
sublink_idstringyesid from partner_list_sublinks.

No output schema declared.

No examples provided.

partner_get_kit ~122

Returns ready texts, a resident email, a move-in text and email to forward to new tenants, desk card and move-in insert wording with the partner’s link, links to the partner’s printable move-in package (move-in insert and QR card PDFs with their own QR and code), plus the house rules for sharing (honest words only, no pressure, never ask residents for phone numbers or door codes).

NameTypeReqDescription
partner_keystring–The partner key from partner_claim_key. On REST send it as "Authorization: Bearer <key>" instead.

No output schema declared.

No examples provided.

partner_get_links ~60

Returns the partner’s share link, typed code, a QR code (SVG) and their dashboard address.

NameTypeReqDescription
partner_keystring–The partner key from partner_claim_key. On REST send it as "Authorization: Bearer <key>" instead.

No output schema declared.

No examples provided.

partner_get_stats ~93

Returns status, visits, signups, free months, paying apartments, collected revenue, earnings by state (on hold, ready, paid, reversed), the share ledger (apartments as codes only, never names or addresses) and payout history. Quote only these numbers.

NameTypeReqDescription
partner_keystring–The partner key from partner_claim_key. On REST send it as "Authorization: Bearer <key>" instead.

No output schema declared.

No examples provided.

partner_list_sublinks ~77

Lists the extra tracked links (one per location, building or staff member) with each one’s visits, apartments and earnings. Every apartment and every dollar rolls up to the partner.

NameTypeReqDescription
partner_keystring–The partner key from partner_claim_key. On REST send it as "Authorization: Bearer <key>" instead.

No output schema declared.

No examples provided.

partner_payout_link ~126

Returns a one-time link to a BuzzMeBro page that sends the person to Stripe’s own secure page, where THEY confirm their identity and add their bank. You never see or type bank details. Payouts start once they have at least $25 ready. First-time setup only: once payouts work, payout changes are made by the partner on their signed-in dashboard. The partner gets a text whenever this link is made.

NameTypeReqDescription
partner_keystring–The partner key from partner_claim_key. On REST send it as "Authorization: Bearer <key>" instead.

No output schema declared.

No examples provided.

partner_program_info ~62

Returns how the partner program works: the 50% share of collected revenue, what counts and what does not, when and how payouts happen, the rules, and the steps to join. Call it first and explain it to the person before applying. Stores nothing.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

partner_rotate_key ~74

Revokes the current partner key and returns a new one (shown once). Use it if the key may have leaked. The partner gets a text whenever the key is replaced.

NameTypeReqDescription
partner_keystring–The partner key from partner_claim_key. On REST send it as "Authorization: Bearer <key>" instead.

No output schema declared.

No examples provided.

partner_send_code ~94

Texts a 6-digit code to the mobile number in the application (never any other number). Ask the person to read it to you, then call partner_confirm_code. Each application gets 3 codes, at least a minute apart.

NameTypeReqDescription
application_idstringyesapplication_id from partner_apply.
application_tokenstringyesapplication_token from partner_apply. Keep it private; it collects the partner key once.

No output schema declared.

No examples provided.

partner_terms_link ~89

Returns a one-time link to the partner terms. Give it to the person: they read the terms and press Accept themselves. You cannot accept for them. When they say it is done, call partner_claim_key.

NameTypeReqDescription
application_idstringyesapplication_id from partner_apply.
application_tokenstringyesapplication_token from partner_apply. Keep it private; it collects the partner key once.

No output schema declared.

No examples provided.

send_phone_code ~103

Texts a 6-digit code to the mobile number given in create_setup (never to any other number). Tell the person a text is coming and ask them to read the code to you, then call confirm_phone_code. Call again only if it has not arrived after a minute; each setup gets 3 codes.

NameTypeReqDescription
setup_idstringyessetup_id from create_setup.
status_tokenstringyesstatus_token from create_setup. Keep it private.

No output schema declared.

No examples provided.

start_checkout ~123

After confirm_phone_code: creates the person’s BuzzMeBro account and apartment and returns payment_url, Stripe’s own secure page where the person approves a card, Apple Pay, Google Pay or Link (with the free month when it applies, nothing is charged until it ends). Give them the link or message_for_the_person; you never see or type card details. Calling it again returns a fresh link for the same apartment.

NameTypeReqDescription
setup_idstringyessetup_id from create_setup.
status_tokenstringyesstatus_token from create_setup. Keep it private.

No output schema declared.

No examples provided.

Install

How do I install the BuzzMeBro MCP server?

BuzzMeBro is a hosted endpoint at https://buzzmebro.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · buzzmebro.com

# add to Claude Code
claude mcp add --transport http com-buzzmebro-buzzmebro 'https://buzzmebro.com/api/mcp'
Common questions

What is the BuzzMeBro MCP server?

BuzzMeBro is an MCP server listed in the public MCP registry as com.buzzmebro/buzzmebro. More than one roommate on your apartment buzzer number; settings decide who rings. Canada. This page covers its hosted endpoint (https://buzzmebro.com/api/mcp).

Is the BuzzMeBro MCP server safe to use?

BuzzMeBro scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the BuzzMeBro MCP server expose?

BuzzMeBro exposes 20 tools: check_building, create_setup, send_phone_code, confirm_phone_code, start_checkout, and 15 more. Their descriptions and schemas cost roughly 2,140 tokens of context every time the server is loaded.

Does the BuzzMeBro MCP server require authentication?

No. We connected to BuzzMeBro without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the BuzzMeBro MCP server still maintained?

BuzzMeBro is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.