Remote MCP · Endpoint

BuzzMeBro MCP server

No. BuzzMeBro answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://buzzmebro.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.buzzmebro/buzzmebro
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
197 ms
Tools exposed
20 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
More than one roommate on your apartment buzzer number; settings decide who rings. Canada.
Listing
From the official MCP registry (active).
Recent checks of BuzzMeBro
CheckedResultHandshake
1 hour agoHandshake completed197 ms
8 days agoHandshake completed230 ms
9 days agoHandshake completed123 ms
11 days agoHandshake completed92 ms
12 days agoHandshake completed106 ms
12 days agoHandshake completed893 ms
14 days agoHandshake completed341 ms
14 days agoHandshake completed118 ms
16 days agoHandshake completed418 ms
19 days agoHandshake completed90 ms
21 days agoHandshake completed135 ms
24 days agoHandshake completed114 ms
26 days agoHandshake completed103 ms
28 days agoHandshake completed122 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with BuzzMeBro and makes no claim about it beyond what these checks measured.