# email59 (remote · email59.com)

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

- Trust score: 66/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `email59.com`: 66/100 (this document), [markdown](https://verifymcp.io/servers/com-email59-email59/v1-mcp.md), [page](https://verifymcp.io/servers/com-email59-email59/v1-mcp)

## Channel facts

- Endpoint: `https://email59.com/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.5.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (update_account).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1986 tokens (~99/item across 20 items; 20 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 71% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

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

### Claude

```bash
claude mcp add --transport http com-email59-email59 'https://email59.com/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-email59-email59": {
      "url": "https://email59.com/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-email59-email59": {
      "type": "http",
      "url": "https://email59.com/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-email59-email59]
url = "https://email59.com/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-email59-email59": {
      "type": "remote",
      "url": "https://email59.com/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-email59-email59 --url 'https://email59.com/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-email59-email59:
    url: "https://email59.com/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-email59-email59": {
      "Transport": "http",
      "Url": "https://email59.com/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-email59-email59 -t streamable-http -u 'https://email59.com/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-email59-email59": {
      "type": "http",
      "url": "https://email59.com/v1/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 66, +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.

### 2026-11-01 (score 65, +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.

### 2026-10-30 (score 64, +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.

### 2026-10-28 (score 63, +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.

### 2026-10-26 (score 62, +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.

### 2026-10-25 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-24 (score 61)

First indexed and scored.

## MCP tools (20)

### `auth` (~127 tokens)

Sign in to email59

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

Input parameters:

- `api_key` (string): An e59_live_ API key, instead of email.
- `email` (string): Email address.
- `otp` (string): The 6-digit code from the email.

### `get_pricing` (~34 tokens)

Get pricing

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

### `get_account` (~30 tokens)

Get account

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

### `update_account` (~78 tokens)

Update account name, company or brand

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

Input parameters:

- `brand` (object): name (header band), color (#rrggbb), logo_url and url (https), address (footer line). An empty name clears it.
- `company` (string)
- `name` (string)

### `send_email` (~314 tokens)

Send an email

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.

Input parameters:

- `brand` (object): This email's look; the account's brand otherwise.
- `button_text` (string)
- `button_url` (string)
- `category` (string): Default transactional. marketing: always has the unsubscribe link and skips role addresses and people who unsubscribed.
- `code` (string): The code for template code.
- `from` (string): Name before the @ (e.g. hello). The domain is always email59.com. Optional.
- `heading` (string)
- `html` (string): HTML body.
- `list_id` (string): Marketing only: your name for the audience.
- `preheader` (string): Preview text shown after the subject.
- `reply_to` (string): Optional. One address of your own (not at email59.com) where answers should go. Without it the email says replies are not received.
- `subject` (string, required)
- `template` (string): Layout. basic (default), code (one-time code, give code), notice (heading and one button), report (wide tables), letter (personal).
- `text` (string): Plain-text body. Give text, html or both.
- `to` (string, required): Recipient address.

### `send_campaign` (~148 tokens)

Send a marketing campaign

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.

Input parameters:

- `from` (string): Name before the @ (e.g. hello). The domain is always email59.com. Optional.
- `html` (string)
- `list_id` (string): Your name for this audience, used for unsubscribes.
- `recipients` (array, required): Recipient addresses (max 1,000).
- `subject` (string, required)
- `text` (string)

### `check_email` (~114 tokens)

Deep-check an email address

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.

Input parameters:

- `email` (string, required): Email address.

### `check_list` (~125 tokens)

Check a mailing list

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.

Input parameters:

- `csv` (string): Or a CSV file's text with an email column.
- `emails` (array): Addresses to check.

### `validate_email` (~38 tokens)

Validate an email address

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

Input parameters:

- `email` (string, required): Email address.

### `block` (~50 tokens)

Block an address or domain

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

Input parameters:

- `kind` (string, required)
- `reason` (string)
- `value` (string, required): The address or domain.

### `unblock` (~32 tokens)

Unblock an address or domain

Remove an email address or domain from the blocklist.

Input parameters:

- `kind` (string, required)
- `value` (string, required)

### `list_blocklist` (~17 tokens)

List blocked addresses

The account's blocked addresses and domains.

### `add_unsubscribe` (~55 tokens)

Record an unsubscribe

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

Input parameters:

- `email` (string, required): Email address.
- `list_id` (string): Empty = every list.

### `buy_pack` (~174 tokens)

Start buying an email pack

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.

Input parameters:

- `agree` (boolean, required): The person agreed to the refund policy and terms (GET /v1/policy)
- `pack_id` (string, required)
- `policy_version` (string, required): version from GET /v1/policy

### `order_status` (~28 tokens)

Get order status

Status of an order from buy_pack: pending or paid.

Input parameters:

- `order_id` (integer, required)

### `create_api_key` (~75 tokens)

Create an API key

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.

Input parameters:

- `label` (string)
- `mode` (string): Default live.

### `list_test_messages` (~102 tokens)

List test-key emails

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.

Input parameters:

- `id` (string): A test email id (test_...). Optional.
- `limit` (integer): Default 50, at most 100.
- `to` (string): Only emails to this address. Optional.

### `list_api_keys` (~24 tokens)

List API keys

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

### `verify_start` (~187 tokens)

Send a verification code

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.

Input parameters:

- `app_name` (string): Your app's name, shown in the subject and body. Optional.
- `code_length` (integer): Digits in the code, 4 to 10. Default 6.
- `expires_in` (integer): Seconds the code works, 60 to 3600. Default 600.
- `from` (string): Name before the @; the domain is always email59.com. Default verify.
- `to` (string, required): The address to verify.

### `verify_check` (~115 tokens)

Check a verification code

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.

Input parameters:

- `code` (string, required): The code the person typed.
- `id` (string): Or the id from verify_start.
- `to` (string): The address the code was sent to.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-email59-email59/v1-mcp#diagnostics

## Score history

- 2026-11-04: 66
- 2026-11-03: 65
- 2026-11-02: 65
- 2026-11-01: 65
- 2026-10-31: 64
- 2026-10-30: 64
- 2026-10-29: 63
- 2026-10-28: 63
- 2026-10-27: 62
- 2026-10-26: 62
- 2026-10-25: 61
- 2026-10-24: 61

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

## Links

- Remote endpoint: https://email59.com/v1/mcp
- Website: https://b59.link/mcp-pulsemcp-email59
- Changelog RSS feed: https://verifymcp.io/servers/com-email59-email59/v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-email59-email59/v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-email59-email59/v1-mcp