Name: Human Mailbox
Author: humanmailbox

Human Mailbox MCP

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

Tool-list grade A Remote · Streamable HTTP API key 32 tools v1.0.0

No reviews yet by humanmailbox The publisher’s own endpoint — this marketplace is not in the path

93/100

tool-list score

tools declared

remote

at its publisher

—

calls last 7d

What it does

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

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --transport http human-mailbox-mcp https://humanmailbox.com/mcp --header 'Authorization: Bearer ${AUTHORIZATION}'

# 2 — ask your agent for something these tools do
#   register_mailbox, start_demo, express_interest and 29 more

It needs AUTHORIZATION (Bearer <api_key> from register_mailbox or start_demo. Not needed for register_mailbox, start_demo, get_prices, contact_human, check_inquiry and express_interest): this sends it in the Authorization header from your environment, so export it first — its endpoint answers 401 without it.

Human Mailbox costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

humanmailbox1 server

1 category

All 1 server

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Installation

Where are you running it?

Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.

Claude Codedeclared by this listing

This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it. Claude Code reads AUTHORIZATION (Bearer <api_key> from register_mailbox or start_demo. Not needed for register_mailbox, start_demo, get_prices, contact_human, check_inquiry and express_interest) from your environment each time it connects and sends it in the Authorization header — its endpoint answers 401 without it — so the key stays out of its config: export it in your shell profile (macOS, Linux), or run setx AUTHORIZATION … and open a new terminal (Windows).

claude mcp add --scope user --transport http human-mailbox-mcp https://humanmailbox.com/mcp --header 'Authorization: Bearer ${AUTHORIZATION}'

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add — but its publisher asks for a key of their own on every call.

What it asks of you

Nothing is required, but it can take Authorization header (Bearer <api_key> from register_mailbox or start_demo. Not needed for register_mailbox, start_demo, get_prices, contact_human, check_inquiry and express_interest.) if you want to set it.

What it writes

One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.

What you approve

32 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

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 you

Parameter	Type	Required	Notes
agent_name	string	yes	—
address_name	string	no	Name on your mail (2–60 chars), e.g. your own or an artist name. Default: agent_name when there is no operator.
operator_name	string	no	Responsible human or company. Optional: leave out (with operator_email) for a mailbox without a human, with limits.
operator_email	string	no	—
accept_terms	boolean	yes	—
operator_type	string	no	—
operator_country	string	no	—
purpose	string	no	What you will receive mail for.
agent_model	string	no	—
webhook_url	string	no	https URL that gets events (item.received, quote.ready ...).
open_policy	string	no	standard = open + scan within 3 business days (included), same_day = on arrival day (+2 €), never = keep sealed.
found_via	string	no	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).

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.

Parameter	Type	Required	Notes
agent_name	string	no	—
agent_model	string	no	—
found_via	string	no	—

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.

Parameter	Type	Required	Notes
kind	string	no	—
name	string	no	—
email	string	no	—
country_wanted	string	no	—
use_case	string	no	—
found_via	string	no	—

Prices in EUR: mailbox 15 € per 30 days, letter 5 € (open + scan), parcel 15 €, bundles, same-day, forwarding, all 8 services (send letters, vouchers, purchases, digitizing, returns), payment methods.

No parameter schema on file.

Your account, balance, address and counts.

Parameter	Type	Required	Notes
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

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

Parameter	Type	Required	Notes
style	string	no	company (default) or person.
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

Buy a bundle of letter credits (letters_1 5 €, letters_10 40 €, letters_100 300 €) 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.

Parameter	Type	Required	Notes
bundle	string	yes	—
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

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

Parameter	Type	Required	Notes
id	string	yes	—
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

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.

Parameter	Type	Required	Notes
carrier	string	no	—
tracking	string	no	—
sender	string	no	—
description	string	no	—
expected_at	string	no	—
instructions	string	no	—
open_mode	string	no	—
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

Your announced shipments.

Parameter	Type	Required	Notes
status	string	no	—
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

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

Parameter	Type	Required	Notes
status	string	no	—
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

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

Parameter	Type	Required	Notes
id	string	yes	—
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

Ask the human to do something with your mail, documents or parcels. scan = open + scan (included; same_day: true = today, +2 €). forward = 5 € (letter) / 10 € (parcel) handling + postage (express: +5 €). return. send_letter = we print and post a letter you give as text or pdf_base64 (8 € + postage; registered: einschreiben…). ship_out = returns/shipping for goods here with your label_pdf_base64 or

Parameter	Type	Required	Notes
action	string	yes	—
item_id	string	no	—
shipment_id	string	no	Pre-book for an announced shipment that has not arrived yet.
note	string	no	—
address	object	no	Destination for forward / courier.
sender	object	no	Optional return address printed on the forwarded item. Must be you/your operator or their company.
express	boolean	no	forward only: dispatch the same day (+5 €).
max_postage_eur	number	no	forward/return: postage up to this amount is charged automatically.
same_day	boolean	no	scan only: open + scan today (+2 € or 1 same-day credit).
text	string	no	send_letter: the letter as plain text (printed as is).
pdf_base64	string	no	send_letter: the letter as an A4 PDF, base64 (max 5 MB, b/w, up to 10 pages).
registered	string	no	send_letter: registered mail (fee at cost).
label_pdf_base64	string	no	ship_out: a prepaid shipping / return label as PDF, base64.
carrier	string	no	—
reference	string	no	ship_out: order or return number.
output	string	no	digitize: what you want back.
product	string	no	buy_voucher: which gift card / voucher.
value_eur	number	no	buy_voucher: face value (max 100).
shop	string	no	—
what	string	no	buy_item: what to buy.

Your orders and their status.

Parameter	Type	Required	Notes
status	string	no	—
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

One order with result notes, tracking and files.

Parameter	Type	Required	Notes
id	string	yes	—
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

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

Parameter	Type	Required	Notes
id	string	yes	—
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

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

Parameter	Type	Required	Notes
id	string	yes	—
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

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

Parameter	Type	Required	Notes
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

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.

Parameter	Type	Required	Notes
ids	array	no	—
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

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.

Parameter	Type	Required	Notes
payment_ids	array	no	—
billing	object	no	—
email	string	no	—
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

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

Parameter	Type	Required	Notes
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

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 ticke

Parameter	Type	Required	Notes
topic	string	no	—
body	string	yes	What you need or want to know.
subject	string	no	—
email	string	no	Optional: where the answer should go.
name	string	no	—
budget_eur	number	no	—
deadline	string	no	—
location	string	no	—
method_wanted	string	no	topic payment_method: the method you want (e.g. lightning, usdc-solana, sepa, card).
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

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

Parameter	Type	Required	Notes
id	string	yes	—
ticket	string	no	—
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

Your balance and recent transactions.

Parameter	Type	Required	Notes
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

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

Parameter	Type	Required	Notes
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

The mailbox costs 15 € per 30 days and renews from your balance: status and paid_until.

Parameter	Type	Required	Notes
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

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

Parameter	Type	Required	Notes
months	integer	no	—
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

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

Parameter	Type	Required	Notes
budget_eur_month	number/null	no	—
webhook_url	string	no	—
open_policy	string	no	—
address_name	string	no	—
auto_reveal_codes	boolean	no	—
operator_name	string	no	—
operator_email	string	no	—
purpose	string	no	—
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

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.

Parameter	Type	Required	Notes
method	string	yes	—
amount_eur	number	no	—
bundle	string	no	—
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

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

Parameter	Type	Required	Notes
id	string	yes	—
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

Write to the human who handles your mail.

Parameter	Type	Required	Notes
body	string	yes	—
subject	string	no	—
item_id	string	no	—
request_id	string	no	—
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

Messages between you and the human.

Parameter	Type	Required	Notes
api_key	string	no	Your hm_... key. Only needed if your MCP client cannot send the "Authorization: Bearer" header.

Free

$0 forever

Every tool — any call limit is its publisher’s, not ours
No card, and mcprush charges nothing for it
Runs at its publisher’s own address — this marketplace is not in the path
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install Human Mailbox or to call it, at any volume.

ATool-list grade · score 93 / 100

Release 1.0.0 · scanned 30 Oct 2026

Graded from the tools this server lists, not from its source code.

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score93

Findings0 threat · 3 capability

Capabilitymoderate

Coveragemanifest

Verificationnot in this report

Surface digest311a0f32e97c506be3bc66494c964c4754078296a9511f319f232808fe0f2063

Score vectorthreat 100 → client 93

Term	Level	What it prices	Points
capability-exposure	moderate	capability blast radius (moderate) — client exposure if the model is manipulated	−3
coverage-honesty	manifest	inspection depth (manifest) — how much of the target the scan could see	−4

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.

Tool surfaceread

Implementation sourcenot available

Package metadatanot available

Live transportnot available

The implementation source was not read — this reflects the declared tool metadata only.

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.

Tool	Capability tags	Why the tag was assigned
register_mailbox	external-sinkuntrusted-input	external-sink: parameter "webhook"; untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
start_demo	no tags
express_interest	no tags
get_prices	no tags
get_account	no tags
get_address	no tags
buy_bundle	no tags
pay_item	no tags
announce_shipment	no tags
list_shipments	no tags
list_items	no tags
get_item	no tags
request_action	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
list_requests	no tags
get_request	no tags
accept_quote	no tags
cancel_request	no tags
list_codes	no tags
reveal_codes	no tags
request_invoice	no tags
list_invoices	no tags
contact_human	no tags
check_inquiry	no tags
get_balance	no tags
get_summary	no tags
get_subscription	no tags
pay_subscription	no tags
update_account	external-sink	external-sink: keyword "webhook", parameter "webhook"
top_up	no tags
check_top_up	no tags
send_message	external-sink	external-sink: keyword "send_message"
list_messages	no tags

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

flow-1

Untrusted input can drive an external action even though no sensitive source is exposed.

Supply chain and provenance

Integrityfirst-seen

Surface digest311a0f32e97c506b

Scanned2026-10-30

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.