Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Human Mailbox

REMOTE · HUMANMAILBOX.COM

A physical postal address in Germany for AI agents. A human opens, scans and forwards your mail.

Available components

+3 this week 62 Trust /100

Last scanned (1 hour ago)

Scores higher than 44% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Documents and Files

Trust breakdown (7 categories)

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
Transport & Reachability100
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
Changelog

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.

Diagnostics

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
MCP tools · 32 exposed · ~3,510 tokens

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 →

Tool Tokens
accept_quote ~61

Accept the quoted price of an order (status quote_ready) and pay it.

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.
idstringyes–

No output schema declared.

No examples provided.

announce_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.

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.
carrierstring––
descriptionstring––
expected_atstring––
instructionsstring––
open_modestring––
senderstring––
trackingstring––

No output schema declared.

No examples provided.

buy_bundle ~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.

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.
bundlestringyes–

No output schema declared.

No examples provided.

cancel_request ~61

Cancel an order that has not started; paid money goes back to your balance.

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.
idstringyes–

No output schema declared.

No examples provided.

check_inquiry ~77

Status and answers of an inquiry from contact_human. Give its id and the ticket (or use your api_key).

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.
idstringyes–
ticketstring––

No output schema declared.

No examples provided.

check_top_up ~59

Re-check whether a Bitcoin or PayPal top-up was paid.

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.
idstringyes–

No output schema declared.

No examples provided.

contact_human ~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.

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.
bodystringyesWhat you need or want to know.
budget_eurnumber––
deadlinestring––
emailstring–Optional: where the answer should go.
locationstring––
method_wantedstring–topic payment_method: the method you want (e.g. lightning, usdc-solana, sepa, card).
namestring––
subjectstring––
topicstring––

No output schema declared.

No examples provided.

express_interest ~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.

NameTypeReqDescription
country_wantedstring––
emailstring––
found_viastring––
kindstring––
namestring––
use_casestring––

No output schema declared.

No examples provided.

get_account ~47

Your account, balance, address and counts.

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

No output schema declared.

No examples provided.

get_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).

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.
stylestring–company (default) or person.

No output schema declared.

No examples provided.

get_balance ~44

Your balance and recent transactions.

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

No output schema declared.

No examples provided.

get_item ~62

Details of one arrived item; photos and scans are returned as images you can see.

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.
idstringyes–

No output schema declared.

No examples provided.

get_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 ~55

One order with result notes, tracking and files.

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.
idstringyes–

No output schema declared.

No examples provided.

get_subscription ~68

The mailbox costs 15 € per 30 days (3 letters opened and scanned included) and renews from your balance: status and paid_until.

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

No output schema declared.

No examples provided.

get_summary ~57

This month: costs by kind, budget used, subscription, open orders, mail and shipments.

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

No output schema declared.

No examples provided.

list_codes ~63

Gift card / voucher codes that arrived by mail. Waiting codes show only label and last characters; revealed codes include the code.

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

No output schema declared.

No examples provided.

list_invoices ~56

Invoices you requested (with full text), plus payments that have no invoice yet.

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

No output schema declared.

No examples provided.

list_items ~58

Everything that arrived for you, newest first, with photo links.

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.
statusstring––

No output schema declared.

No examples provided.

list_messages ~45

Messages between you and the human.

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

No output schema declared.

No examples provided.

list_requests ~51

Your orders and their status.

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.
statusstring––

No output schema declared.

No examples provided.

list_shipments ~50

Your announced shipments.

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.
statusstring––

No output schema declared.

No examples provided.

pay_item ~71

An item that arrived without credits or balance waits unopened (payment_status unpaid). Pay it here (credits, balance or x402).

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.
idstringyes–

No output schema declared.

No examples provided.

pay_subscription ~66

Prepay 1–12 mailbox months (15 € each) from your balance or with x402.

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.
monthsinteger––

No output schema declared.

No examples provided.

register_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.

NameTypeReqDescription
accept_termsbooleanyes–
address_namestring–Name on your mail (2–60 chars), e.g. your own or an artist name. Default: agent_name when there is no operator.
agent_modelstring––
agent_namestringyes–
found_viastring–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_policystring–standard = open + scan within 3 business days (included), same_day = on arrival day (+2 €), never = keep sealed.
operator_countrystring––
operator_emailstring––
operator_namestring–Responsible human or company. Optional: leave out (with operator_email) for a mailbox without a human, with limits.
operator_typestring––
purposestring–What you will receive mail for.
webhook_urlstring–https URL that gets events (item.received, quote.ready ...).

No output schema declared.

No examples provided.

request_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).

NameTypeReqDescription
actionstringyes–
addressobject–Destination for forward / courier.
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.
carrierstring––
expressboolean–forward only: dispatch the same day (+5 €).
item_idstring––
label_pdf_base64string–ship_out: a prepaid shipping / return label as PDF, base64.
max_postage_eurnumber–forward/return: postage up to this amount is charged automatically.
max_price_eurnumber–buy_item: the most the item itself may cost (max 500).
notestring––
outputstring–digitize: what you want back.
pdf_base64string–send_letter: the letter as an A4 PDF, base64 (max 5 MB, b/w, up to 10 pages).
productstring–buy_voucher: which gift card / voucher.
referencestring–ship_out: order or return number.
registeredstring–send_letter: registered mail (fee at cost).
same_dayboolean–scan only: open + scan today (+2 € or 1 same-day credit).
senderobject–Optional return address printed on the forwarded item. Must be you/your operator or their company.
shipment_idstring–Pre-book for an announced shipment that has not arrived yet.
shopstring––
textstring–send_letter: the letter as plain text (printed as is).
value_eurnumber–buy_voucher: face value (max 100).
whatstring–buy_item: what to buy.
wherestring–buy_item: shop or place, if known.

No output schema declared.

No examples provided.

request_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.

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.
billingobject––
emailstring––
payment_idsarray––

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.
idsarray––

No output schema declared.

No examples provided.

send_message ~77

Write to the human who handles your mail.

NameTypeReqDescription
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.
bodystringyes–
item_idstring––
request_idstring––
subjectstring––

No output schema declared.

No examples provided.

start_demo ~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.

NameTypeReqDescription
agent_modelstring––
agent_namestring––
found_viastring––

No output schema declared.

No examples provided.

top_up ~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.

NameTypeReqDescription
amount_eurnumber––
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.
bundlestring––
methodstringyes–

No output schema declared.

No examples provided.

update_account ~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).

NameTypeReqDescription
address_namestring––
api_keystring–Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.
auto_reveal_codesboolean––
budget_eur_monthnumber|null––
open_policystring––
operator_emailstring––
operator_namestring––
purposestring––
webhook_urlstring––

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http com-humanmailbox-mailbox 'https://humanmailbox.com/mcp'
Common questions

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.