_ registry / mcp streamable-http

buzzmebro

https://buzzmebro.com

Registry code: 2a46834843e0972e

api record

BuzzMeBro gives an apartment its own local phone number so the building’s lobby buzzer rings every roommate’s phone at once; whoever answers presses the usual digit to open the door. It is for renters and condo residents in Canada (Toronto/GTA and Greater Vancouver first).

Use these tools when your user wants their apartment buzzer to ring more than one phone, needs a buzzer number because they have no landline, is moving in with roommates, or asks you to buy or set up BuzzMeBro for them.

endpoint
https://buzzmebro.com/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is buzzmebro live?
Not measured yet: the hub has not completed a check of this server.
Is buzzmebro free to use?
Not measured yet.
What tools does buzzmebro have?
6 tools: check_building, create_setup, send_phone_code, confirm_phone_code, start_checkout, get_setup_status.
Is buzzmebro safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
unknown
uptime
—
latency
—

last good check

priced tools
0

of 6 tools

_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
6 never probed 0 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • check_building unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "postal_code"
  ],
  "properties": {
    "postal_code": {
      "type": "string",
      "maxLength": 12,
      "minLength": 3,
      "description": "The apartment building’s postal code, e.g. \"M4B 1B3\". Canadian postal codes only for now."
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • create_setup unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "postal_code",
    "unit",
    "mobile_phone"
  ],
  "properties": {
    "unit": {
      "type": "string",
      "maxLength": 32,
      "minLength": 1,
      "description": "Their apartment or unit number as the lobby panel lists it, e.g. \"1502\", \"B\" or \"PH3\"."
    },
    "agent_name": {
      "type": "string",
      "maxLength": 64,
      "description": "Optional: your name as the person knows you (e.g. \"ChatGPT\", \"Claude\"), shown on their link page."
    },
    "postal_code": {
      "type": "string",
      "maxLength": 12,
      "minLength": 3,
      "description": "The apartment building’s postal code, e.g. \"M4B 1B3\". Canadian postal codes only for now."
    },
    "mobile_phone": {
      "type": "string",
      "maxLength": 32,
      "minLength": 7,
      "description": "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."
    },
    "referral_code": {
      "type": "string",
      "maxLength": 20,
      "description": "Optional BuzzMeBro referral code from a friend."
    }
  },
  "additionalProperties": false
}
    arguments 39 lines
  • send_phone_code unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "setup_id",
    "status_token"
  ],
  "properties": {
    "setup_id": {
      "type": "string",
      "format": "uuid",
      "description": "setup_id from create_setup."
    },
    "status_token": {
      "type": "string",
      "description": "status_token from create_setup. Keep it private."
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • confirm_phone_code unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "setup_id",
    "status_token",
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "The digits from the BuzzMeBro text, e.g. \"482913\"."
    },
    "setup_id": {
      "type": "string",
      "format": "uuid",
      "description": "setup_id from create_setup."
    },
    "status_token": {
      "type": "string",
      "description": "status_token from create_setup. Keep it private."
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • start_checkout unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "setup_id",
    "status_token"
  ],
  "properties": {
    "setup_id": {
      "type": "string",
      "format": "uuid",
      "description": "setup_id from create_setup."
    },
    "status_token": {
      "type": "string",
      "description": "status_token from create_setup. Keep it private."
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • get_setup_status unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "setup_id",
    "status_token"
  ],
  "properties": {
    "setup_id": {
      "type": "string",
      "format": "uuid",
      "description": "setup_id from create_setup."
    },
    "status_token": {
      "type": "string",
      "description": "status_token from create_setup. Keep it private."
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 2a46834843e0972e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/2a46834843e0972e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/2a46834843e0972e/badge.svg)](https://brick.blue/agent/2a46834843e0972e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.