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.

email59

REMOTE · EMAIL59.COM

Send transactional email from AI agents: sign up by email code, no domain or DNS setup.

Available components

+3 this week 66 Trust /100

Last scanned (18 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Communication

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 Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1986 tokens (~99/item across 20 items; 20 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 71% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 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.

  • 25 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 24 Oct 26 61

    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 4 Nov 2026 · Probed https://email59.com/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=email59.com CN=YE2,O=Let's Encrypt,C=US 12 Sept 2026 11 Dec 2026 ECDSA 256 ECDSA-SHA384 60c9218f1faeb0bff09448964b993f4972e
SANs: email59.com, www.email59.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of email59.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
email59.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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://email59.com/v1/mcp Verified 200
http (plaintext) http://email59.com/v1/mcp HTTPS enforced 301 https://email59.com/v1/mcp
MCP tools · 20 exposed · ~1,867 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
add_unsubscribe ~55

Record an opt-out. Campaigns to that list (or every list, if list_id is empty) skip the address.

NameTypeReqDescription
emailstringyesEmail address.
list_idstring–Empty = every list.

No output schema declared.

No examples provided.

auth ~127

Sign up or sign in to email59. Pass email to have a 6-digit code emailed, then call again with email and otp to get a session key (a new email is signed up with 200 free emails a day). Or pass api_key to swap an API key for a session key. Send the key as the HTTP header 'Authorization: Bearer <session_key>'.

NameTypeReqDescription
api_keystring–An e59_live_ API key, instead of email.
emailstring–Email address.
otpstring–The 6-digit code from the email.

No output schema declared.

No examples provided.

block ~50

Block an email address or a whole domain for this account. Sends to it are refused.

NameTypeReqDescription
kindstringyes–
reasonstring––
valuestringyesThe address or domain.

No output schema declared.

No examples provided.

buy_pack ~174

Start buying a pack (pack_5 = $5, pack_10 = $10, pack_50 = $50; each $1 adds 3,636 email credits, which don't renew and last until used, plus a purchase fee of 5% or at least $0.50 at checkout; GET /v1/pricing has the totals). Returns a checkout_url for a person to pay; the credits arrive once the payment clears. First show the person the refund policy and terms from GET /v1/policy; pass agree=true and its version only after they agree.

NameTypeReqDescription
agreebooleanyesThe person agreed to the refund policy and terms (GET /v1/policy)
pack_idstringyes–
policy_versionstringyesversion from GET /v1/policy

No output schema declared.

No examples provided.

check_email ~114

Free deep check of an email address, no sign-in needed: format, provider username rules, disposable and role addresses, and the domain's MX, SPF, DMARC, DKIM, MTA-STS, TLS-RPT and BIMI records. Returns a report with a score (0-99, likelihood the address is real) and a verdict (likely_valid, risky, likely_invalid, unknown). Gmail, Outlook and other big providers skip DNS. No email is sent.

NameTypeReqDescription
emailstringyesEmail address.

No output schema declared.

No examples provided.

check_list ~125

List check for a mailing list: up to 1,000 different addresses a call, as emails or the text of a CSV (the column headed email). One status each: valid, risky, role, disposable, no_mx or invalid, with a reason, plus counts per status. Format, provider rules and one MX lookup per domain; no email is sent. Daily limit per account; the answer's quota shows what is left today.

NameTypeReqDescription
csvstring–Or a CSV file's text with an email column.
emailsarray–Addresses to check.

No output schema declared.

No examples provided.

create_api_key ~75

Create a long-lived API key (max 10 per account). It is shown only once. mode 'test' makes an e59_test_ key for staging and CI: its sends are accepted and stored, never delivered, and use no allowance.

NameTypeReqDescription
labelstring––
modestring–Default live.

No output schema declared.

No examples provided.

get_account ~30

The signed-in account: email, daily_limit, sent_today, remaining_today, credits_remaining, resets_at.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_pricing ~34

Free daily emails (renewed every day), email credits per dollar, and the packs on sale. No sign-in needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_api_keys ~24

The account's API keys (ids and labels, never the keys themselves).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_blocklist ~17

The account's blocked addresses and domains.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_test_messages ~102

Emails sent with a test key (e59_test_...), newest first: accepted, stored, never delivered. Pass id for one email with its html and text (a verify_start code is in there), or to to filter by recipient.

NameTypeReqDescription
idstring–A test email id (test_...). Optional.
limitinteger–Default 50, at most 100.
tostring–Only emails to this address. Optional.

No output schema declared.

No examples provided.

order_status ~28

Status of an order from buy_pack: pending or paid.

NameTypeReqDescription
order_idintegeryes–

No output schema declared.

No examples provided.

send_campaign ~148

Send a marketing email to up to 1,000 recipients; the unsubscribe link is added for you. Invalid, role, blocked or unsubscribed recipients are skipped and cost nothing; each accepted recipient uses 1 email of today's allowance. A campaign that doesn't fit what's left today is refused whole.

NameTypeReqDescription
fromstring–Name before the @ (e.g. hello). The domain is always email59.com. Optional.
htmlstring––
list_idstring–Your name for this audience, used for unsubscribes.
recipientsarrayyesRecipient addresses (max 1,000).
subjectstringyes–
textstring––

No output schema declared.

No examples provided.

send_email ~314

Send one email to one recipient: transactional (receipt, code, alert) or marketing (category). It goes out as HTML in a branded template with a text part; give text, html or both. Uses 1 email of today's allowance. Many recipients at once: send_campaign.

NameTypeReqDescription
brandobject–This email's look; the account's brand otherwise.
button_textstring––
button_urlstring––
categorystring–Default transactional. marketing: always has the unsubscribe link and skips role addresses and people who unsubscribed.
codestring–The code for template code.
fromstring–Name before the @ (e.g. hello). The domain is always email59.com. Optional.
headingstring––
htmlstring–HTML body.
list_idstring–Marketing only: your name for the audience.
preheaderstring–Preview text shown after the subject.
reply_tostring–Optional. One address of your own (not at email59.com) where answers should go. Without it the email says replies are not received.
subjectstringyes–
templatestring–Layout. basic (default), code (one-time code, give code), notice (heading and one button), report (wide tables), letter (personal).
textstring–Plain-text body. Give text, html or both.
tostringyesRecipient address.

No output schema declared.

No examples provided.

unblock ~32

Remove an email address or domain from the blocklist.

NameTypeReqDescription
kindstringyes–
valuestringyes–

No output schema declared.

No examples provided.

update_account ~78

Set the name, company or brand (the look of every email the account sends) on the account.

NameTypeReqDescription
brandobject–name (header band), color (#rrggbb), logo_url and url (https), address (footer line). An empty name clears it.
companystring––
namestring––

No output schema declared.

No examples provided.

validate_email ~38

Check an address before sending. Verdicts: ok, invalid, no_mx, disposable, role.

NameTypeReqDescription
emailstringyesEmail address.

No output schema declared.

No examples provided.

verify_check ~115

Check a code from verify_start. Give to (checks the newest code sent there) or id, and code. Returns valid true or false and a status: approved, wrong_code, expired, too_many_attempts (5 wrong codes lock it), already_used, replaced or not_found. A right code works once. Uses no allowance.

NameTypeReqDescription
codestringyesThe code the person typed.
idstring–Or the id from verify_start.
tostring–The address the code was sent to.

No output schema declared.

No examples provided.

verify_start ~187

Email a one-time verification code to an address (sign-up, sign-in, confirming an email). email59 makes the code, sends it, limits resends and expires it; the code is never returned to you. Returns an id. Uses 1 email of today's allowance. A new code to the same address replaces the one waiting there. Then call verify_check with what the person typed.

NameTypeReqDescription
app_namestring–Your app's name, shown in the subject and body. Optional.
code_lengthinteger–Digits in the code, 4 to 10. Default 6.
expires_ininteger–Seconds the code works, 60 to 3600. Default 600.
fromstring–Name before the @; the domain is always email59.com. Default verify.
tostringyesThe address to verify.

No output schema declared.

No examples provided.

Install

How do I install the email59 MCP server?

email59 is a hosted endpoint at https://email59.com/v1/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 · email59.com

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

What is the email59 MCP server?

email59 is an MCP server listed in the public MCP registry as com.email59/email59. Send transactional email from AI agents: sign up by email code, no domain or DNS setup. This page covers its hosted endpoint (https://email59.com/v1/mcp).

Is the email59 MCP server safe to use?

email59 scores 66 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 email59 MCP server expose?

email59 exposes 20 tools: auth, get_pricing, get_account, update_account, send_email, and 15 more. Their descriptions and schemas cost roughly 1,867 tokens of context every time the server is loaded.

Does the email59 MCP server require authentication?

No. We connected to email59 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the email59 MCP server still maintained?

email59 is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.