# BuzzMeBro (remote · buzzmebro.com)

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

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

> **Recent critical change**: Authorization (2026-10-14). See the changelog below before you install this server.

## Components

- remote · `buzzmebro.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-buzzmebro-buzzmebro/api-mcp.md), [page](https://verifymcp.io/servers/com-buzzmebro-buzzmebro/api-mcp)

## Channel facts

- Endpoint: `https://buzzmebro.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (partner_disable_sublink).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http com-buzzmebro-buzzmebro 'https://buzzmebro.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-buzzmebro-buzzmebro": {
      "url": "https://buzzmebro.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-buzzmebro-buzzmebro": {
      "type": "http",
      "url": "https://buzzmebro.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-buzzmebro-buzzmebro]
url = "https://buzzmebro.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-buzzmebro-buzzmebro": {
      "type": "remote",
      "url": "https://buzzmebro.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-buzzmebro-buzzmebro --url 'https://buzzmebro.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-buzzmebro-buzzmebro:
    url: "https://buzzmebro.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-buzzmebro-buzzmebro": {
      "Transport": "http",
      "Url": "https://buzzmebro.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-buzzmebro-buzzmebro -t streamable-http -u 'https://buzzmebro.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-buzzmebro-buzzmebro": {
      "type": "http",
      "url": "https://buzzmebro.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-18 (score 70, +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.

### 2026-10-16 (score 69, +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.

### 2026-10-15 (score 68, 0)

- [security] 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
- [functional regression] 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”
- [cosmetic] “partner_apply” added an optional parameter “payouts_off”
- [cosmetic] “partner_apply” reworded the description of “persona”

### 2026-10-14 (score 68, −6)

- [critical regression] Authorization: partial → fail
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] New tool “partner_rotate_key”, which the server declares destructive
- [functional improvement] Schema quality: 189 → 140
- [functional improvement] 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”

### 2026-10-13 (score 74)

First indexed and scored.

## MCP tools (20)

### `check_building` (~83 tokens)

Check a building

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.

Input parameters:

- `postal_code` (string, required): The apartment building’s postal code, e.g. "M4B 1B3". Canadian postal codes only for now.

### `create_setup` (~244 tokens)

Set up BuzzMeBro for the person

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.

Input parameters:

- `agent_name` (string): Optional: your name as the person knows you (e.g. "ChatGPT", "Claude"), shown on their link page.
- `mobile_phone` (string, required): The 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_code` (string, required): The apartment building’s postal code, e.g. "M4B 1B3". Canadian postal codes only for now.
- `referral_code` (string): Optional BuzzMeBro referral code from a friend.
- `unit` (string, required): Their apartment or unit number as the lobby panel lists it, e.g. "1502", "B" or "PH3".

### `send_phone_code` (~103 tokens)

Text the person a confirmation code

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.

Input parameters:

- `setup_id` (string, required): setup_id from create_setup.
- `status_token` (string, required): status_token from create_setup. Keep it private.

### `confirm_phone_code` (~99 tokens)

Confirm the code the person read to you

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.

Input parameters:

- `code` (string, required): The digits from the BuzzMeBro text, e.g. "482913".
- `setup_id` (string, required): setup_id from create_setup.
- `status_token` (string, required): status_token from create_setup. Keep it private.

### `start_checkout` (~123 tokens)

Get the payment page

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.

Input parameters:

- `setup_id` (string, required): setup_id from create_setup.
- `status_token` (string, required): status_token from create_setup. Keep it private.

### `get_setup_status` (~122 tokens)

Check setup progress

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.

Input parameters:

- `setup_id` (string, required): setup_id from create_setup.
- `status_token` (string, required): status_token from create_setup. Keep it private.

### `partner_program_info` (~62 tokens)

Explain the BuzzMeBro partner program

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.

### `partner_apply` (~221 tokens)

Start a partner application for the person

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.

Input parameters:

- `building` (string): Optional: the building or company they work with.
- `email` (string, required): The person’s email.
- `employer_ok` (boolean): If they work for a building or concierge company: has their employer allowed it?
- `mobile_phone` (string, required): The person’s own Canadian mobile number. We text it a code.
- `name` (string, required): The person’s name.
- `payouts_off` (boolean): 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.
- `persona` (string, required): The 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…

### `partner_send_code` (~94 tokens)

Text the person a confirmation code

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.

Input parameters:

- `application_id` (string, required): application_id from partner_apply.
- `application_token` (string, required): application_token from partner_apply. Keep it private; it collects the partner key once.

### `partner_confirm_code` (~75 tokens)

Confirm the code the person read to you

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

Input parameters:

- `application_id` (string, required): application_id from partner_apply.
- `application_token` (string, required): application_token from partner_apply. Keep it private; it collects the partner key once.
- `code` (string, required): The digits from the text.

### `partner_terms_link` (~89 tokens)

Get the terms page for the person

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.

Input parameters:

- `application_id` (string, required): application_id from partner_apply.
- `application_token` (string, required): application_token from partner_apply. Keep it private; it collects the partner key once.

### `partner_claim_key` (~91 tokens)

Collect the partner key (once)

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.

Input parameters:

- `application_id` (string, required): application_id from partner_apply.
- `application_token` (string, required): application_token from partner_apply. Keep it private; it collects the partner key once.

### `partner_get_links` (~60 tokens)

The partner’s link, code and QR

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

Input parameters:

- `partner_key` (string): The partner key from partner_claim_key. On REST send it as "Authorization: Bearer <key>" instead.

### `partner_get_kit` (~122 tokens)

Ready-to-send messages for residents

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).

Input parameters:

- `partner_key` (string): The partner key from partner_claim_key. On REST send it as "Authorization: Bearer <key>" instead.

### `partner_get_stats` (~93 tokens)

The partner’s numbers

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.

Input parameters:

- `partner_key` (string): The partner key from partner_claim_key. On REST send it as "Authorization: Bearer <key>" instead.

### `partner_payout_link` (~126 tokens)

Link for the person to add their bank on Stripe

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.

Input parameters:

- `partner_key` (string): The partner key from partner_claim_key. On REST send it as "Authorization: Bearer <key>" instead.

### `partner_list_sublinks` (~77 tokens)

The partner’s tracked links

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.

Input parameters:

- `partner_key` (string): The partner key from partner_claim_key. On REST send it as "Authorization: Bearer <key>" instead.

### `partner_create_sublink` (~102 tokens)

Add a tracked link

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.

Input parameters:

- `label` (string, required): A name for the link, e.g. "King St location".
- `partner_key` (string): The partner key from partner_claim_key. On REST send it as "Authorization: Bearer <key>" instead.

### `partner_disable_sublink` (~80 tokens)

Switch off a tracked link

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

Input parameters:

- `partner_key` (string): The partner key from partner_claim_key. On REST send it as "Authorization: Bearer <key>" instead.
- `sublink_id` (string, required): id from partner_list_sublinks.

### `partner_rotate_key` (~74 tokens)

Replace the partner key

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.

Input parameters:

- `partner_key` (string): The partner key from partner_claim_key. On REST send it as "Authorization: Bearer <key>" instead.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-buzzmebro-buzzmebro/api-mcp#diagnostics

## Score history

- 2026-10-18: 70
- 2026-10-17: 69
- 2026-10-16: 69
- 2026-10-15: 68
- 2026-10-14: 68
- 2026-10-13: 74

## 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.

## Links

- Remote endpoint: https://buzzmebro.com/api/mcp
- Website: https://buzzmebro.com/agents
- Changelog RSS feed: https://verifymcp.io/servers/com-buzzmebro-buzzmebro/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-buzzmebro-buzzmebro/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-buzzmebro-buzzmebro/api-mcp