BumbleBox
REMOTE · API.BUMBLEBOX.AI
Search and triage all your mailboxes; draft replies and campaigns; send only as you allow.
Available components
Last scanned (19 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Communication
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1424 tokens (~83/item across 17 items; 17 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 18 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
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
- Tool “draft_reply” rewrote its description, which is the text the model reads security
- Tool “search_emails” rewrote its description, which is the text the model reads security
- Tool “send_reply” rewrote its description, which is the text the model reads security
- 23 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 22 Oct 26 75
First indexed and scored.
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 4 Nov 2026 · Probed https://api.bumblebox.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bumblebox.ai | CN=YE2,O=Let's Encrypt,C=US | 9 Sept 2026 | 8 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5ec805e072f6f4fa60067b435a7f4919c80 |
| SANs: *.bumblebox.ai, bumblebox.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.bumblebox.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| bumblebox.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://api.bumblebox.ai/.well-known/oauth-protected-resource/api/mcp", scope="mail:read mail:draft mail:send mail:organize blog:write"
Bearer resource_metadata="https://api.bumblebox.ai/.well-known/oauth-protected-resource/api/mcp", scope="mail:read mail:draft mail:send mail:organize blog:write"Protected resource metadata
| Document | https://api.bumblebox.ai/.well-known/oauth-protected-resource/api/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://api.bumblebox.ai/api/mcp |
| Authorisation server | https://api.bumblebox.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.bumblebox.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://api.bumblebox.ai/api/mcp | HTTPS enforced | 301 | https://api.bumblebox.ai/api/mcp |
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 →
archive_email Archive an email ~58
Moves one inbox email to its mailbox's archive folder, on the mail server too. Undone by restore_to_inbox. Nothing is deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| email_id | string | yes | Email id, as returned by search_emails or list_to_answer. |
| Name | Type | Req | Description |
|---|---|---|---|
| moved | object | yes | – |
No examples provided.
create_campaign_draft Write a campaign draft (not sent) ~110
Writes one draft inside an existing campaign, to one recipient (added to the campaign list if new), from the campaign's sender. Nothing is sent: the draft waits for the user to validate the campaign send in BumbleBox.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Plain-text body. |
| mission_id | string | yes | Campaign id, as returned by list_missions. |
| name | string | – | Recipient name, for a new prospect. |
| subject | string | yes | – |
| to | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| draft | object | yes | – |
No examples provided.
draft_reply Prepare a reply (not sent) ~137
Saves the text as the reply draft of a received email, from the address the email was written to (a brand address or the mailbox). needsIdentity: that address cannot send until the user verifies it in BumbleBox. Nothing is sent: the draft waits in BumbleBox (Pilotage › prepared replies) until the user reviews it and clicks Send. Saving again replaces the previous draft of the same email.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Plain-text reply body. |
| email_id | string | yes | Email id, as returned by search_emails or list_to_answer. |
| subject | string | – | Defaults to "Re: <original subject>". |
| Name | Type | Req | Description |
|---|---|---|---|
| draft | object | yes | – |
No examples provided.
get_email Read an email ~54
One email in full: sender, recipients, date, subject, plain-text body, attachment names, folder and BumbleBox classification.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Email id, as returned by search_emails or list_to_answer. |
| Name | Type | Req | Description |
|---|---|---|---|
| object | yes | – |
No examples provided.
list_calendar_events List calendar events ~47
Events of the connected Google calendars between two dates (default: the next 7 days, at most 62 days).
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | – |
| to | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | yes | – |
No examples provided.
list_campaign_drafts List the drafts of a campaign ~69
The drafts of one campaign that wait for the user to validate them in BumbleBox (recipient, subject, plain-text body, sender), newest first, with the true totals.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| mission_id | string | yes | Campaign id, as returned by list_missions. |
| Name | Type | Req | Description |
|---|---|---|---|
| counts | object | yes | – |
| drafts | array | yes | – |
No examples provided.
list_folders List mail folders ~31
The folders of each connected mailbox, as last synced. Trash, spam, sent and drafts are left out.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| mailboxes | array | yes | – |
No examples provided.
list_missions List campaigns ~43
The user's prospection campaigns (missions), most recently active first, with the number of drafts waiting, emails sent and prospects who replied.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| missions | array | yes | – |
No examples provided.
list_replies_to_validate Campaign replies waiting for the user ~52
Replies received on campaigns that still need the user: prepared reply drafts waiting for validation, and replies with no answer yet (with the stored AI triage: kind, summary, whether a human is needed).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| drafts | array | yes | – |
| pending | – | yes | – |
No examples provided.
list_to_answer Emails waiting for a reply ~34
Received emails BumbleBox classified as needing a reply and still in the inbox, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | – |
No examples provided.
move_email Move an email to a folder ~73
Moves one inbox email to an existing folder of the same mailbox (see list_folders), on the mail server too. No folder is created. Undone by restore_to_inbox.
| Name | Type | Req | Description |
|---|---|---|---|
| email_id | string | yes | Email id, as returned by search_emails or list_to_answer. |
| folder | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| moved | object | yes | – |
No examples provided.
restore_to_inbox Put an email back in the inbox ~51
Moves an archived, filed or trashed email back to the inbox, on the mail server too.
| Name | Type | Req | Description |
|---|---|---|---|
| email_id | string | yes | Email id, as returned by search_emails or list_to_answer. |
| Name | Type | Req | Description |
|---|---|---|---|
| email_id | string | yes | – |
| restored | number | yes | – |
No examples provided.
search_contacts Search contacts ~57
Contacts BumbleBox knows from the mail history (name, address, organization domain, exchange counts, last exchanges, VIP mark, note), matched on name, address or domain.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| contacts | array | yes | – |
No examples provided.
search_emails Search emails ~83
Searches every connected mailbox (sender, subject, preview), newest first. Operators: from:, subject:, before:YYYY-MM-DD, after:YYYY-MM-DD, in:sent (only what the user sent, from any mailbox or alias); the rest is free text. Deleted emails are not returned.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
send_reply Reply to the sender ~168
Replies to the sender of one received email, and only to them (no Cc, no Bcc, no attachment), from the address the email was written to. What happens next is the level the user set in BumbleBox for this kind of reply: a draft, a reply waiting for one tap (the default), or a reply that leaves after a delay the user can cancel. Anything that commits the user (amounts, bank details, acceptance, contracts, dates, links) always waits for the user, and so does a reply from an address the user has not verified (needsIdentity). The result says which one applied.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Plain-text reply body. |
| email_id | string | yes | Email id, as returned by search_emails or list_to_answer. |
| Name | Type | Req | Description |
|---|---|---|---|
| reply | object | yes | – |
No examples provided.
trash_email Put an email in the trash ~115
Moves one inbox email to its mailbox's trash when BumbleBox certifies it as noise (spam, newsletter, promotion, with a unanimous safety vote and no known contact or action word). Any other email is not moved: it becomes a proposal the user confirms in one tap in BumbleBox. Never a permanent deletion; undone by restore_to_inbox.
| Name | Type | Req | Description |
|---|---|---|---|
| email_id | string | yes | Email id, as returned by search_emails or list_to_answer. |
| reason | string | – | Why, shown to the user with a proposal. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
update_campaign_draft Edit a campaign draft (not sent) ~87
Changes the subject, body or recipient of a draft that is still a draft. Nothing is sent, and a draft the user already validated cannot be changed.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | – |
| draft_id | string | yes | – |
| mission_id | string | yes | Campaign id, as returned by list_missions. |
| subject | string | – | – |
| to | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| draft | object | yes | – |
No examples provided.
How do I install the BumbleBox MCP server?
BumbleBox is a hosted endpoint at https://api.bumblebox.ai/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 · api.bumblebox.ai
claude mcp add --transport http ai-bumblebox-mail 'https://api.bumblebox.ai/api/mcp'
What is the BumbleBox MCP server?
BumbleBox is an MCP server listed in the public MCP registry as ai.bumblebox/mail. Search and triage all your mailboxes; draft replies and campaigns; send only as you allow. This page covers its hosted endpoint (https://api.bumblebox.ai/api/mcp).
Is the BumbleBox MCP server safe to use?
BumbleBox scores 81 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 BumbleBox MCP server expose?
BumbleBox exposes 17 tools: search_emails, get_email, list_to_answer, search_contacts, list_folders, and 12 more. Their descriptions and schemas cost roughly 1,269 tokens of context every time the server is loaded.
Does the BumbleBox MCP server require authentication?
Yes. BumbleBox asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the BumbleBox MCP server still maintained?
BumbleBox is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.