Remote MCP · Endpoint

BumbleBox MCP server

No. BumbleBox answered an MCP handshake 33 minutes ago.

UpLast checked 33 minutes ago

Server URL

https://api.bumblebox.ai/api/mcp

The last check completed an MCP handshake.

Registry name
ai.bumblebox/mail
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
386 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Search and triage all your mailboxes; draft replies and campaigns; send only as you allow.
Listing
From the official MCP registry (active).
Recent checks of BumbleBox
CheckedResultHandshake
33 minutes agoHandshake completed386 ms
3 days agoHandshake completed366 ms
13 days agoHandshake completed355 ms
13 days agoHandshake completed361 ms
15 days agoHandshake completed347 ms
16 days agoHandshake completed358 ms
17 days agoHandshake completed359 ms
18 days agoHandshake completed356 ms
18 days agoHandshake completed357 ms
20 days agoHandshake completed401 ms
22 days agoHandshake completed463 ms
25 days agoHandshake completed401 ms
27 days agoHandshake completed425 ms

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

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 BumbleBox and makes no claim about it beyond what these checks measured.