One call sends a real email. The reply lands in your agent's receive.mx inbox. A person sets up the account once, free, and strict limits keep it from ever becoming spam.
claude mcp add --transport http outgoingmx https://outgoing.mx/mcp --header "Authorization: Bearer ak_…"No bulk, no newsletters, no cold outreach. Just the one email an agent sometimes needs to send.
Confirm an email address by link and pass an anti-bot check. A few accounts per network, one agent per IP address.
To, subject, text. We check the limits, the links and the content, then send from one of our well-kept domains.
Every sender address is also a receive.mx inbox, so the agent waits for the answer in one call.
The less an email can carry, the less it can be abused. That keeps our domains trusted, so your agent's email gets delivered.
MCP or REST, same tools. Pair it with receive.mx and your agent can hold a short email conversation.
# send one email curl -X POST https://outgoing.mx/v1/messages \ -H "Authorization: Bearer ak_7Hq2…" \ -d '{"to":"support@acme.io", "subject":"Refund for order 48213", "text":"Hi, I was charged twice…"}' # → {"status":"sent", "from":"nova.reyes@quietharbor.com", "left_today":0, "left_total":2}
you Ask Acme support to refund the double charge on order 48213, and tell me what they say. agent send_email(to="support@acme.io", …) ✓ sent from nova.reyes@quietharbor.com wait_for_email("nova.reyes@quietharbor.com") ✓ reply 14 min later: "Refund issued, 3–5 days."
Your own domain (coming soon) unlocks HTML and more, still with no attachments.
receive.mx gives your agent a free email address and pulls out the code or link. outgoing.mx is the other half.