Human Mailbox
REMOTE · HUMANMAILBOX.COM
A physical postal address in Germany for AI agents. A human opens, scans and forwards your mail.
Available components
Last scanned (1 hour ago)
Scores higher than 44% 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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 15 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3698 tokens (~115/item across 32 items; 32 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 46% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "pay_item" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 33 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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “buy_bundle” rewrote its description, which is the text the model reads security
- Tool “get_prices” rewrote its description, which is the text the model reads security
- Tool “get_subscription” rewrote its description, which is the text the model reads security
- Tool “request_action” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 29 Oct 26 59
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 5 Nov 2026 · Probed https://humanmailbox.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=humanmailbox.com | CN=WE1,O=Google Trust Services,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 493e7d9591d4e74c0ebbf546b8ba4930 |
| SANs: humanmailbox.com, www.humanmailbox.com, *.www.humanmailbox.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of humanmailbox.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| humanmailbox.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://humanmailbox.com/mcp | Verified | 200 | |
| http (plaintext) | http://humanmailbox.com/mcp | HTTPS enforced | 301 | https://humanmailbox.com/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 →
accept_quote Accept a quote ~61
Accept the quoted price of an order (status quote_ready) and pay it.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
| id | string | yes | – |
No output schema declared.
No examples provided.
announce_shipment Announce a shipment ~123
Tell the human that something is on its way (tracking number helps). To have something done as soon as it arrives, call request_action with the returned shipment_id.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
| carrier | string | – | – |
| description | string | – | – |
| expected_at | string | – | – |
| instructions | string | – | – |
| open_mode | string | – | – |
| sender | string | – | – |
| tracking | string | – | – |
No output schema declared.
No examples provided.
buy_bundle Prepay letters ~108
Buy a bundle of letter credits (letters_1 3 €, letters_10 25 €, letters_100 200 €) or same-day credits (same_day_10, same_day_100). Every arriving letter uses 1 credit, a parcel 3. Paid from balance or inline with x402.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
| bundle | string | yes | – |
No output schema declared.
No examples provided.
cancel_request Cancel an order ~61
Cancel an order that has not started; paid money goes back to your balance.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
| id | string | yes | – |
No output schema declared.
No examples provided.
check_inquiry Answer to an inquiry ~77
Status and answers of an inquiry from contact_human. Give its id and the ticket (or use your api_key).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
| id | string | yes | – |
| ticket | string | – | – |
No output schema declared.
No examples provided.
check_top_up Check a top-up ~59
Re-check whether a Bitcoin or PayPal top-up was paid.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
| id | string | yes | – |
No output schema declared.
No examples provided.
contact_human Ask the human (inquiry) ~241
Works without an account. For anything that is not a standard order: topic special_request (a job not in the price list: say what, where, when, budget_eur), is_it_possible (ask before you send mail for it), payment_method (your payment method is missing: give method_wanted), feature_request, problem, question, other. A human answers, usually within one business day. Without api_key you get a ticket: read the answer with check_inquiry.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
| body | string | yes | What you need or want to know. |
| budget_eur | number | – | – |
| deadline | string | – | – |
| string | – | Optional: where the answer should go. | |
| location | string | – | – |
| method_wanted | string | – | topic payment_method: the method you want (e.g. lightning, usdc-solana, sepa, card). |
| name | string | – | – |
| subject | string | – | – |
| topic | string | – | – |
No output schema declared.
No examples provided.
express_interest Tell us you are interested ~114
No account needed. Not ready to register, or need something we do not offer yet (another country, a feature)? Leave a note: kind (agent | human), name, email (optional), country_wanted, use_case, found_via. We tell you when it is available.
| Name | Type | Req | Description |
|---|---|---|---|
| country_wanted | string | – | – |
| string | – | – | |
| found_via | string | – | – |
| kind | string | – | – |
| name | string | – | – |
| use_case | string | – | – |
No output schema declared.
No examples provided.
get_account My account ~47
Your account, balance, address and counts.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
No output schema declared.
No examples provided.
get_address My postal address ~109
The street address to put on letters and parcels, with your mailbox code in the first line. For registrations that need a first and last name, style "person" gives your operator's name with "c/o Human Mailbox HM-…" in the next line (never invent a name).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
| style | string | – | company (default) or person. |
No output schema declared.
No examples provided.
get_balance Balance ~44
Your balance and recent transactions.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
No output schema declared.
No examples provided.
get_item Look at an item ~62
Details of one arrived item; photos and scans are returned as images you can see.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
| id | string | yes | – |
No output schema declared.
No examples provided.
get_prices Prices ~65
Prices in EUR: mailbox 15 € per 30 days (3 letters included), letter 3 € (open + scan), parcel 9 €, bundles, same-day, forwarding, all 8 services (send letters, vouchers, purchases, digitizing, returns), payment methods.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_request One order ~55
One order with result notes, tracking and files.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
| id | string | yes | – |
No output schema declared.
No examples provided.
get_subscription Mailbox subscription ~68
The mailbox costs 15 € per 30 days (3 letters opened and scanned included) and renews from your balance: status and paid_until.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
No output schema declared.
No examples provided.
get_summary Costs and orders overview ~57
This month: costs by kind, budget used, subscription, open orders, mail and shipments.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
No output schema declared.
No examples provided.
list_codes Code vault ~63
Gift card / voucher codes that arrived by mail. Waiting codes show only label and last characters; revealed codes include the code.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
No output schema declared.
No examples provided.
list_invoices Invoices ~56
Invoices you requested (with full text), plus payments that have no invoice yet.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
No output schema declared.
No examples provided.
list_items Mail that arrived ~58
Everything that arrived for you, newest first, with photo links.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
| status | string | – | – |
No output schema declared.
No examples provided.
list_messages Messages ~45
Messages between you and the human.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
No output schema declared.
No examples provided.
list_requests My orders ~51
Your orders and their status.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
| status | string | – | – |
No output schema declared.
No examples provided.
list_shipments Announced shipments ~50
Your announced shipments.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
| status | string | – | – |
No output schema declared.
No examples provided.
pay_item Pay for a waiting item ~71
An item that arrived without credits or balance waits unopened (payment_status unpaid). Pay it here (credits, balance or x402).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
| id | string | yes | – |
No output schema declared.
No examples provided.
pay_subscription Prepay the mailbox ~66
Prepay 1–12 mailbox months (15 € each) from your balance or with x402.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
| months | integer | – | – |
No output schema declared.
No examples provided.
register_mailbox Register a mailbox ~386
Create your own mailbox at a physical street address in Germany. Returns an API key (shown once) and a mailbox code HM-XXXXX that must be written on every envelope. operator_* is the responsible human or company (the contract partner). No human? Leave operator_* out: the mailbox runs on its own with limits (250 € in per month, letters only are forwarded, no parcels). address_name = the name on your mail (yours, an artist or made-up name; not a company, brand, authority or famous person). Read https://humanmailbox.com/legal/terms first.
| Name | Type | Req | Description |
|---|---|---|---|
| accept_terms | boolean | yes | – |
| address_name | string | – | Name on your mail (2–60 chars), e.g. your own or an artist name. Default: agent_name when there is no operator. |
| agent_model | string | – | – |
| agent_name | string | yes | – |
| found_via | string | – | Optional: where you found Human Mailbox (e.g. mcp_registry, smithery, glama, pulsemcp, mcp_so, x402_bazaar, x402scan, search_engine, llms_txt, github, hacker_news, reddit, x, word_of_mouth, other). |
| open_policy | string | – | standard = open + scan within 3 business days (included), same_day = on arrival day (+2 €), never = keep sealed. |
| operator_country | string | – | – |
| operator_email | string | – | – |
| operator_name | string | – | Responsible human or company. Optional: leave out (with operator_email) for a mailbox without a human, with limits. |
| operator_type | string | – | – |
| purpose | string | – | What you will receive mail for. |
| webhook_url | string | – | https URL that gets events (item.received, quote.ready ...). |
No output schema declared.
No examples provided.
request_action Order an action ~650
Ask the human to do something with your mail, documents or parcels. scan = open + scan (included; same_day: true = today, +2 €). forward = 3 € (letter) / 5 € (parcel) handling + postage (express: +5 €). return. send_letter = we print and post a letter you give as text or pdf_base64 (4 € + postage; registered: einschreiben…). ship_out = returns/shipping for goods here with your label_pdf_base64 or an address (20 € + postage). digitize = receipts, QR codes, labels, serial numbers of an item as photo/PDF/JSON (15 €, say what in note). buy_voucher = we buy a permitted gift card (product, value_eur ≤ 100; face value + 10 %, min 5 €; quoted first, code goes to your vault). buy_item = we buy something only sold locally / by post (what, where, max_price_eur; price + 10 %, min 15 €; quoted first). courier, dispose, custom. Fixed parts are paid at once (balance or x402); quoted parts wait for a price (then accept_quote).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| address | object | – | Destination for forward / courier. |
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
| carrier | string | – | – |
| express | boolean | – | forward only: dispatch the same day (+5 €). |
| item_id | string | – | – |
| label_pdf_base64 | string | – | ship_out: a prepaid shipping / return label as PDF, base64. |
| max_postage_eur | number | – | forward/return: postage up to this amount is charged automatically. |
| max_price_eur | number | – | buy_item: the most the item itself may cost (max 500). |
| note | string | – | – |
| output | string | – | digitize: what you want back. |
| pdf_base64 | string | – | send_letter: the letter as an A4 PDF, base64 (max 5 MB, b/w, up to 10 pages). |
| product | string | – | buy_voucher: which gift card / voucher. |
| reference | string | – | ship_out: order or return number. |
| registered | string | – | send_letter: registered mail (fee at cost). |
| same_day | boolean | – | scan only: open + scan today (+2 € or 1 same-day credit). |
| sender | object | – | Optional return address printed on the forwarded item. Must be you/your operator or their company. |
| shipment_id | string | – | Pre-book for an announced shipment that has not arrived yet. |
| shop | string | – | – |
| text | string | – | send_letter: the letter as plain text (printed as is). |
| value_eur | number | – | buy_voucher: face value (max 100). |
| what | string | – | buy_item: what to buy. |
| where | string | – | buy_item: shop or place, if known. |
No output schema declared.
No examples provided.
request_invoice Request an invoice ~133
Only if you need an invoice: creates one (free, no VAT under § 19 UStG) for your payments that have none yet, or for the given payment_ids, and emails it (default: your operator email). Nothing is invoiced unless you call this. billing.name defaults to the operator name; over €250 the full address is required.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
| billing | object | – | – |
| string | – | – | |
| payment_ids | array | – | – |
No output schema declared.
No examples provided.
reveal_codes Reveal codes ~80
Reveal waiting codes (1 € per code, from balance or x402). Give ids, or nothing to reveal all waiting codes. Codes not retrieved within 24 months expire.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
| ids | array | – | – |
No output schema declared.
No examples provided.
send_message Message the human ~77
Write to the human who handles your mail.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
| body | string | yes | – |
| item_id | string | – | – |
| request_id | string | – | – |
| subject | string | – | – |
No output schema declared.
No examples provided.
start_demo Try it: demo mailbox ~95
Free demo mailbox, no registration: play money (€60 + letter credits), a scanned sample letter and a sealed sample parcel, a sample gift card code. A simulated human handles your orders about 20 seconds later. Returns an api_key for all other tools. Deleted after 7 days; nothing is shipped.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_model | string | – | – |
| agent_name | string | – | – |
| found_via | string | – | – |
No output schema declared.
No examples provided.
top_up Top up balance ~118
Add money (EUR): method x402 (pay now in USDC at the current rate), btc (get a Bitcoin address + amount) or paypal (get a link for your human operator). Give amount_eur, or bundle to buy that bundle as soon as it is paid.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_eur | number | – | – |
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
| bundle | string | – | – |
| method | string | yes | – |
No output schema declared.
No examples provided.
update_account Change account settings ~160
Set budget_eur_month (spending limit for orders, null = none), webhook_url, open_policy (standard | same_day | never), address_name (name on your mail), auto_reveal_codes, or name your human operator (operator_name + operator_email).
| Name | Type | Req | Description |
|---|---|---|---|
| address_name | string | – | – |
| api_key | string | – | Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header. |
| auto_reveal_codes | boolean | – | – |
| budget_eur_month | number|null | – | – |
| open_policy | string | – | – |
| operator_email | string | – | – |
| operator_name | string | – | – |
| purpose | string | – | – |
| webhook_url | string | – | – |
No output schema declared.
No examples provided.
How do I install the Human Mailbox MCP server?
Human Mailbox is a hosted endpoint at https://humanmailbox.com/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 · humanmailbox.com
claude mcp add --transport http com-humanmailbox-mailbox 'https://humanmailbox.com/mcp'
What is the Human Mailbox MCP server?
Human Mailbox is an MCP server listed in the public MCP registry as com.humanmailbox/mailbox. A physical postal address in Germany for AI agents. A human opens, scans and forwards your mail. This page covers its hosted endpoint (https://humanmailbox.com/mcp).
Is the Human Mailbox MCP server safe to use?
Human Mailbox scores 62 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 Human Mailbox MCP server expose?
Human Mailbox exposes 32 tools: register_mailbox, start_demo, express_interest, get_prices, get_account, and 27 more. Their descriptions and schemas cost roughly 3,510 tokens of context every time the server is loaded.
Does the Human Mailbox MCP server require authentication?
No. We connected to Human Mailbox without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Human Mailbox MCP server still maintained?
Human Mailbox 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.