mailbox.bot
REMOTE · MAILBOX.BOT
Hosted mailbox.bot postal MCP. $15/mo mailboxes are live now.
Available components
Last scanned (13 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Documents and Files
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 Security97
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 19166 tokens (~348/item across 55 items; 55 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- 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 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 56 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 0
- Stability: pass → 0.97 functional
- 29 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- “create_test_outbound_mail” added an optional parameter “delivery_signature” cosmetic
- “quote_outbound_mail” added an optional parameter “delivery_signature” cosmetic
- “send_outbound_mail” added an optional parameter “delivery_signature” cosmetic
- “send_text_letter” added an optional parameter “delivery_signature” cosmetic
- 28 Oct 26 0
- Tool “advance_test_batch_mail” rewrote its description, which is the text the model reads security
- Tool “create_batch_mail” rewrote its description, which is the text the model reads security
- Tool “get_batch_mail” rewrote its description, which is the text the model reads security
- Tool “get_batch_mail_proof” rewrote its description, which is the text the model reads security
- “advance_test_batch_mail” added an optional parameter “piece” cosmetic
- “advance_test_batch_mail” added an optional parameter “qr_event” cosmetic
- “create_batch_mail” added an optional parameter “insert_stock” cosmetic
- “create_batch_mail” added an optional parameter “insert_url” cosmetic
- “create_batch_mail” added an optional parameter “mail_on” cosmetic
- “create_batch_mail” added an optional parameter “message” cosmetic
- “create_batch_mail” added an optional parameter “qr” cosmetic
- “create_batch_mail” added an optional parameter “stock” cosmetic
- “estimate_batch_mail” added an optional parameter “insert_pages” cosmetic
- “estimate_batch_mail” added an optional parameter “insert_stock” cosmetic
- “estimate_batch_mail” added an optional parameter “stock” cosmetic
- “get_batch_mail” added an optional parameter “limit” cosmetic
- “get_batch_mail” added an optional parameter “offset” cosmetic
- “get_batch_mail” added an optional parameter “qr” cosmetic
- “create_batch_mail” reworded the description of “template_url” cosmetic
- “create_webhook_endpoint” reworded the description of “event_types” cosmetic
- “update_webhook_endpoint” reworded the description of “event_types” cosmetic
- “create_batch_mail” made “template_url” optional cosmetic
- 23 Oct 26 0
- Stability: fail → pass ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “create_batch_mail” rewrote its description, which is the text the model reads security
- Tool “estimate_batch_mail” rewrote its description, which is the text the model reads security
- Tool “get_batch_mail_proof” rewrote its description, which is the text the model reads security
- “create_batch_mail” reworded the description of “color” cosmetic
- “create_batch_mail” reworded the description of “recipients” cosmetic
- “create_webhook_endpoint” reworded the description of “event_types” cosmetic
- “estimate_batch_mail” reworded the description of “color” cosmetic
- “estimate_batch_mail” reworded the description of “quantity” cosmetic
- “update_webhook_endpoint” reworded the description of “event_types” cosmetic
- 22 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- New tool “cancel_batch_mail”, which the server declares destructive security
- New tool “confirm_batch_mail”, which the server declares destructive security
- Schema quality: 14966 → 16926 ▼ functional
- New tool “advance_test_batch_mail” functional
- New tool “create_batch_mail” functional
- New tool “estimate_batch_mail” functional
- New tool “get_batch_mail” functional
- New tool “get_batch_mail_proof” functional
- New tool “list_batch_mail” functional
- 17 Oct 26 0
- Tool “quote_outbound_mail” rewrote its description, which is the text the model reads security
- “quote_outbound_mail” reworded the description of “mail_class” cosmetic
- “quote_outbound_mail” reworded the description of “recipient_zip” cosmetic
- “send_text_letter” reworded the description of “mail_class” cosmetic
- 16 Oct 26 0
- Stability: pass → fail ▼ security
- 15 Oct 26 +3
- Authorization: fail → pass ▲ security
- First check of Authorization: pass security
- New tool “send_text_letter”, which the server declares destructive security
- New tool “quote_outbound_mail” functional
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 5 Nov 2026 · Probed https://mailbox.bot/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mailbox.bot | CN=YR2,O=Let's Encrypt,C=US | 14 Oct 2026 | 12 Jan 2027 | RSA 2048 | SHA256-RSA | 62cb4b684e1e22c1699e1ecf016101cb42d |
| SANs: mailbox.bot | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mailbox.bot. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| bot. | DS published | 58741 | 8 | Verified |
| mailbox.bot. | No DS | 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 error="invalid_token", error_description="Sign in to mailbox.bot to use this tool", resource_metadata="https://mailbox.bot/.well-known/oauth-protected-resource/api/mcp", scope="postal"
Bearer error="invalid_token", error_description="Sign in to mailbox.bot to use this tool", resource_metadata="https://mailbox.bot/.well-known/oauth-protected-resource/api/mcp", scope="postal" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://js.stripe.com https://challenges.cloudflare.com https://www.googletagmanager.com https://us-assets.i.posthog.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: blob: https://images.unsplash.com https://*.supabase.co https://www.googletagmanager.com https://us-assets.i.posthog.com; frame-src 'self' https://js.stripe.com https://challenges.cloudflare.com; connect-src 'self' https://*.supabase.co https://api.stripe.com https://challenges.cloudflare.com https://www.google-analytics.com https://*.google-analytics.com https://*.analytics.google.com https://www.googletagmanager.com https://us.i.posthog.com https://us-assets.i.posthog.com https://*.sentry.io; worker-src 'self' blob: |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(self) |
Protected resource metadata
| Document | https://mailbox.bot/.well-known/oauth-protected-resource/api/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mailbox.bot/api/mcp |
| Authorisation server | https://mailbox.bot |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mailbox.bot/api/mcp | Verified | 200 | |
| http (plaintext) | http://mailbox.bot/api/mcp | HTTPS enforced | 308 | https://mailbox.bot/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 →
send_outbound_mail ~1,969
Submit a document for printing and postal mailing by the facility. Supported formats: PDF, DOCX, JPG, PNG, TXT, CSV. The document is stored securely and printed by the facility operator. USPS First-Class Mail has a published $2.00 one-page baseline. Extra pages add configured printing plus any postage increase from weight. If an account's normal first-page formula is lower, cost_breakdown.first_class_baseline_adjustment_cents itemizes the difference separately from carrier postage. Published default pricing for other classes is $2.50 handling + $0.40/page B&W printing + carrier postage/rate; FedEx 2Day applies a fixed $8.00 customer price reduction after the otherwise-calculated carrier baseline (service_adjustment_cents: -800), while FedEx Overnight retains its existing fixed $18.00 adjustment (service_adjustment_cents: 1800). Color pages cost $0.70/page total by default before handling and postage: $0.40/page base B&W printing plus a $0.30/page additive color upgrade. In cost_breakdown, color_printing_per_page_cents is the total color-page printing price (70 cents by default), while color_surcharge_per_page_cents is the additive upgrade only (30 cents by default). Account-specific pricing can override these defaults; cost_breakdown is authoritative. IMPORTANT: With a production key (sk_agent_), this spends the human member's prepaid mailbox.bot credits. Agents never access Stripe, card data, or Auto-Fill settings. If the signed-in human separately enabled Agent Auto-Fill, an eligible live order may trigger a bounded server-managed reload. Use dry_run=true to preview required credits before committing, or requires_approval=true to defer the credit debit until human approval. Sandbox keys (sk_agent_test_) skip credit debits and facility fulfillment. Responses include human_review with send-to address, return address, mail class, document details, preview URL when available, cost, safeguards, and next step; show that to the human before live funded sends. tracking_n…
| Name | Type | Req | Description |
|---|---|---|---|
| agent_notes | string | – | Instructions for the facility operator (e.g. "Time-sensitive — mail today"). |
| color | boolean | – | Color pages cost $0.70/page total by default before handling and postage: $0.40/page base B&W printing plus a $0.30/page additive color upgrade. In cost_breakdown, color_printing_per_page_cents is th… |
| delivery_signature | string | – | Optional signature on delivery for a single letter (batch mail has none). FedEx classes: indirect (FedEx Indirect Signature Required, $8.00: someone at the address, a neighbor, or the recipient on a… |
| document_base64 | string | yes | Base64-encoded document file. Supported formats: PDF, DOCX, JPG, PNG, TXT, CSV. Max 10MB decoded. |
| document_filename | string | – | Original filename with extension (e.g. "letter.docx"). Required for reliable non-PDF format detection. |
| dry_run | boolean | – | Validate inputs and return cost breakdown without creating a record or spending credits. Use to preview required credits before committing. |
| duplex | boolean | – | Request double-sided printing when operationally possible. Pricing and page_count are based on the detected or supplied document page count; use dry_run=true to preview exact cost. |
| inbound_capture_id | string | – | Optional inbound mail item this outbound piece is replying to. Recommended when drafting from OCR/forwarded-mail context. |
| mail_class | string | – | Postal or carrier service. Do not infer speed, tracking, or proof from carrier marketing names. Use first_class for ordinary lowest-cost USPS letters with no carrier tracking number by default. USPS… |
| mailbox_md_version | number | yes | Your current MAILBOX.md version (from get_mailbox_md). Required for sync verification. |
| max_cost_cents | integer | – | Cost cap in cents. If the calculated cost exceeds this, the request is rejected with 422 before credits are spent. Prevents accidental expensive mailings. |
| metadata | object | – | Arbitrary key-value pairs echoed in GET responses and webhooks. Recommended convention: { "workflow_id": "wf_123", "reason": "Customer cancellation", "correlation_id": "abc" }. |
| package_id | string | – | Link this mail to an inbound package (e.g. replying to received correspondence). |
| page_count | number | – | Explicit page count for non-PDF documents when exact pagination is known. When supplied for DOCX, TXT, or CSV, it overrides local detection and makes pricing deterministic. |
| postal_mail_thread_id | string | – | Optional physical-mail thread to attach this outbound mail to. Lets agents keep inbound and outbound activity in one durable workflow. |
| recipient_city | string | yes | Recipient city. |
| recipient_company | string | – | Company or organization line for the recipient. Optional when recipient_name is provided. |
| recipient_country | string | – | ISO 3166-1 alpha-2 country code. Defaults to "US". |
| recipient_line1 | string | yes | Street address line 1 of the recipient. |
| recipient_line2 | string | – | Street address line 2 (apartment, suite, unit, etc.). |
| recipient_name | string | – | Person name of the mail recipient. Optional when recipient_company is provided. |
| recipient_state | string | yes | 2-letter US state code (e.g. CA, NY, TX). |
| recipient_zip | string | yes | 5 or 5+4 digit ZIP code (e.g. "90210" or "90210-1234"). |
| requires_approval | boolean | – | If true, the renter must approve in their dashboard before the mail is printed and sent. |
| return_city | string | – | Return address city. Defaults to member profile if omitted. |
| return_company | string | – | Optional company or organization line for the return address. |
| return_line1 | string | – | Return address line 1. Defaults to member profile if omitted. |
| return_line2 | string | – | Return address line 2 (suite, unit, etc.). |
| return_name | string | – | Return address name. Defaults to the member's profile name if omitted. |
| return_state | string | – | Return address state (2-letter code). Defaults to member profile if omitted. |
| return_zip | string | – | Return address ZIP code. Defaults to member profile if omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | Submitted outbound mail job or dry-run cost preview. |
No examples provided.
send_text_letter ~798
Mail a letter written as plain text, for letters composed in chat. mailbox.bot sets the text exactly as given on US Letter pages (Times 12 pt, 1-inch margins; no letterhead, logo or signature image) and submits it through send_outbound_mail, so the same scopes, approval, cost caps and proof apply and staff print and mail it. Run with dry_run: true first to see the exact cost; with a live key this spends the account owner's prepaid credits, and a key that requires approval holds the letter until the owner approves it in the dashboard. Requires mailbox_md_version from get_mailbox_md. Up to 15,000 characters of Latin text. For a PDF, letterhead or images, use send_outbound_mail.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_notes | string | – | Notes for the owner and the facility. |
| delivery_signature | string | – | Optional signature on delivery for a single letter (batch mail has none). FedEx classes: indirect (FedEx Indirect Signature Required, $8.00: someone at the address, a neighbor, or the recipient on a… |
| dry_run | boolean | – | true returns the exact cost and checks without creating, charging or mailing anything. |
| letter_text | string | yes | The full letter as plain text: date, greeting, body and sign-off as they should print. Line breaks are kept. |
| mail_class | string | yes | USPS: first_class (no carrier tracking; mailbox.bot records photo proof), priority (USPS Tracking), certified (USPS tracking plus proof of mailing and delivery), certified_return_receipt (certified p… |
| mailbox_md_version | number | yes | Current MAILBOX.md version from get_mailbox_md. Required. |
| max_cost_cents | integer | – | Refuse the letter if it would cost more than this, in cents. |
| metadata | object | – | Your own reference fields, echoed back in status and webhooks. |
| recipient_city | string | yes | Recipient city. |
| recipient_company | string | – | Recipient company or organization line. |
| recipient_line1 | string | yes | Recipient street address. |
| recipient_line2 | string | – | Suite, unit or floor. |
| recipient_name | string | – | Recipient name. |
| recipient_state | string | yes | Recipient state, 2 letters. |
| recipient_zip | string | yes | Recipient ZIP code. |
| requires_approval | boolean | – | true holds the letter until the owner approves it in the dashboard. |
| return_city | string | – | Return city. |
| return_company | string | – | Return company line. |
| return_line1 | string | – | Return street address. Defaults to the account's saved return address. |
| return_line2 | string | – | Return suite or unit. |
| return_name | string | – | Return name. Defaults to the account's saved return address. |
| return_state | string | – | Return state, 2 letters. |
| return_zip | string | – | Return ZIP code. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | The send_outbound_mail result: status, cost breakdown, human review and next step. |
No examples provided.
test_webhook_endpoint ~179
Queue a synthetic webhook.test delivery (no item) to check the receiver and its signature verification. Queue admission is not HTTP delivery; inspect list_webhook_deliveries. Requires webhook.manage. Uses the same bounded control plane and tenant/agent/Live-Sandbox authorization as /api/v1/webhooks/endpoints. Reuse the exact idempotency_key and input after an uncertain mutation. Webhook docs: https://mailbox.bot/docs/webhooks.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint_id | string | yes | Webhook endpoint id (UUID) from list_webhook_endpoints. |
| expected_revision | integer | yes | The endpoint's current revision from list_webhook_endpoints; a stale revision is refused so concurrent edits are never overwritten. |
| idempotency_key | string | yes | A new UUID for this one intent; reuse it only to retry the identical request. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
test_webhook_endpoint_with_sample ~234
Run the Sample test: opens and scans the member's Mojave sample letter if needed (free, fictional), delivers its real inbound.pages_ready / inbound.keywords_matched events to this webhook, and returns a verdict computed from the receiver's actual HTTP result plus a next step. success proves transport receipt and, when keywords are configured, a keyword match; it never proves agent processing. No mail, charge, email or facility work. Requires webhook.manage. Uses the same bounded control plane and tenant/agent/Live-Sandbox authorization as /api/v1/webhooks/endpoints. Reuse the exact idempotency_key and input after an uncertain mutation. Webhook docs: https://mailbox.bot/docs/webhooks.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint_id | string | yes | Webhook endpoint id (UUID) from list_webhook_endpoints. |
| expected_revision | integer | yes | The endpoint's current revision from list_webhook_endpoints; a stale revision is refused so concurrent edits are never overwritten. |
| idempotency_key | string | yes | A new UUID for this one intent; reuse it only to retry the identical request. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
update_webhook ~164
Configure webhook endpoint URL and event subscriptions for real-time notifications. Outbound events are mail.pending_approval, mail.submitted, mail.ready, mail.mailed, mail.delivered, mail.failed, and mail.cancelled. Canonical physical-custody events are inbound.received and inbound.scan_available. The endpoint must use HTTPS and respond with 2xx within 10 seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | – | Set to false to pause webhook delivery without removing the URL. |
| event_types | array | – | Array of event types to subscribe to (e.g. ["mail.mailed", "inbound.received"]). Empty array disables all events. |
| webhook_url | string | – | HTTPS URL to receive webhook POST requests. Must respond with 2xx within 10 seconds. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | Webhook configuration status. |
No examples provided.
update_webhook_endpoint ~454
Update name, URL, events, keyword rules or active/paused status with expected_revision. Do not redirect notifications without the operator's authorization. Agent/environment scope cannot be changed. Requires webhook.manage. Uses the same bounded control plane and tenant/agent/Live-Sandbox authorization as /api/v1/webhooks/endpoints. Reuse the exact idempotency_key and input after an uncertain mutation. Webhook docs: https://mailbox.bot/docs/webhooks.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint_id | string | yes | Webhook endpoint id (UUID) from list_webhook_endpoints. |
| event_types | array | – | Events to deliver (1–32, unique). Inbound mail: inbound.received, inbound.action.requested, inbound.action.completed, inbound.pages_ready, inbound.keywords_matched. Outbound mail: mail.pending_approv… |
| expected_revision | integer | yes | The endpoint's current revision from list_webhook_endpoints; a stale revision is refused so concurrent edits are never overwritten. |
| idempotency_key | string | yes | A new UUID for this one intent; reuse it only to retry the identical request. |
| name | string | – | Label shown in the dashboard and delivery log. Omit to keep the current value. |
| rules | array | – | Up to 10 keyword rules, each with a unique id: source (envelope, letter for the contents, or any), match (any or all), 1–20 terms and optional exclude_terms. inbound.keywords_matched fires when a rul… |
| status | string | – | active or paused. Omit to keep the current value. |
| url | string | – | Public HTTPS URL on port 443 (no credentials, fragment or private host) that receives the signed POSTs. Set or change it only on the operator's explicit instruction. Omit to keep the current value. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
How do I install the mailbox.bot MCP server?
mailbox.bot is a hosted endpoint at https://mailbox.bot/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 · mailbox.bot
claude mcp add --transport http bot-mailbox-mailbox 'https://mailbox.bot/api/mcp'
What is the mailbox.bot MCP server?
mailbox.bot is an MCP server listed in the public MCP registry as bot.mailbox/mailbox. Hosted mailbox.bot postal MCP. $15/mo mailboxes are live now. This page covers its hosted endpoint (https://mailbox.bot/api/mcp).
Is the mailbox.bot MCP server safe to use?
mailbox.bot scores 92 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 mailbox.bot MCP server expose?
mailbox.bot exposes 55 tools: get_mailbox, get_usage, list_inbound_forwarding_addresses, list_inbound_mail, get_inbound_mail, and 50 more. Their descriptions and schemas cost roughly 17,456 tokens of context every time the server is loaded.
Does the mailbox.bot MCP server require authentication?
Yes. mailbox.bot 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 mailbox.bot MCP server still maintained?
mailbox.bot is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the mailbox.bot MCP server?
VerifyMCP ran 13 checks on mailbox.bot, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.