https://mailbox.bot/api/mcp
Remote
v1.0.1
Published by mailbox.bot — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
Physical mail API for AI agents. Send letters, certified mail, postcards from code via MCP.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Untrusted-input tools ([list_facility_conversations]) co-exist with external-action tools ([list_inbound_forwarding_addresses, update_webhook, send_outbound_mail, create_test_outbound_mail, advance_test_outbound_mail]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [list_facility_conversations] → sinks [list_inbound_forwarding_addresses, update_webhook, send_outbound_mail, create_test_outbound_mail, advance_test_
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow list_facility_conversations → list_inbound_forwarding_addresses
Tool "update_webhook" takes a URL/host parameter "webhook_url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).
Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.
Location: tool update_webhook · inputSchema.properties.webhook_url
Each tool and what it can reach — enumerated from the running server.
advance_test_outbound_mailnetwork egresscreate_test_outbound_mailnetwork egresslist_facility_conversationsingests untrusted inputlist_inbound_forwarding_addressesnetwork egresssend_outbound_mailnetwork egressupdate_webhooknetwork egressadd_noteno sensitive capabilityadd_tagno sensitive capabilitycancel_outbound_mailno sensitive capabilitycreate_ruleno sensitive capabilityget_facility_messagesno sensitive capabilityget_inbound_mailno sensitive capabilityget_mailboxno sensitive capabilityget_mailbox_mdno sensitive capabilityget_outbound_mailno sensitive capabilityget_packageno sensitive capabilityget_package_photosno sensitive capabilityget_postal_threadno sensitive capabilityget_scan_resultsno sensitive capabilityget_usageno sensitive capabilitylist_inbound_mailno sensitive capabilitylist_outbound_mailno sensitive capabilitylist_packagesno sensitive capabilitylist_postal_threadsno sensitive capabilitypropose_mailbox_md_editno sensitive capabilityregister_expectedno sensitive capabilityrequest_actionno sensitive capabilityrequest_scanno sensitive capabilitysend_facility_messageno sensitive capabilityupdate_actionno sensitive capabilityCross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.1 latest |
A 97/100 | 2 | 1.10.0 | 2026-07-25 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan https://mailbox.bot/api/mcp --online
One key, 100+ models — chat with any LLM and generate video, images, speech. Free trial at 370.ai.
Security scan results for the Adeu MCP server.
Security scan results for the Agentcanary MCP server.
Signal-first Bitcoin intelligence: sovereign, hiring & hashrate signals over MCP.
WhatsApp® reminders and rescheduling for Calendly. Public read-only MCP endpoint.
Security scan results for the Chat MCP server.