Dead Simple Email
REMOTE · API.DEADSIMPLE.EMAIL · 3 COMPONENTS · SCANNED SEP 20
Give an agent its own inbox: send, receive, and pull signup codes from real email.
Recent critical change
Authorization (30 Jul 2026). See the changelog before you install this server.
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the Dead Simple Email MCP server?
Dead Simple Email is a hosted endpoint at https://api.deadsimple.email/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 · api.deadsimple.email
claude mcp add --transport http email-deadsimple-dead-simple-email 'https://api.deadsimple.email/mcp'
{
"mcpServers": {
"email-deadsimple-dead-simple-email": {
"url": "https://api.deadsimple.email/mcp"
}
}
} {
"servers": {
"email-deadsimple-dead-simple-email": {
"type": "http",
"url": "https://api.deadsimple.email/mcp"
}
}
} [mcp_servers.email-deadsimple-dead-simple-email] url = "https://api.deadsimple.email/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"email-deadsimple-dead-simple-email": {
"type": "remote",
"url": "https://api.deadsimple.email/mcp",
"enabled": true
}
}
} openclaw mcp add email-deadsimple-dead-simple-email --url 'https://api.deadsimple.email/mcp' --transport streamable-http
mcp_servers:
email-deadsimple-dead-simple-email:
url: "https://api.deadsimple.email/mcp" {
"McpServers": {
"email-deadsimple-dead-simple-email": {
"Transport": "http",
"Url": "https://api.deadsimple.email/mcp"
}
}
} assistant mcp add email-deadsimple-dead-simple-email -t streamable-http -u 'https://api.deadsimple.email/mcp'
{
"mcpServers": {
"email-deadsimple-dead-simple-email": {
"type": "http",
"url": "https://api.deadsimple.email/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 −39
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: 0.93 → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: fail → pass ▲ security
- First check of Authorization: partial security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 1 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- Authorization: unverified → fail ▼ critical
- Tool “delete_inbox” is now declared destructive security
- Server version: 1.28.1 → 1.26.0 functional
- Tool “create_inbox” changed its title: Create Inbox cosmetic
- Tool “delete_inbox” changed its title: Delete Inbox cosmetic
- Tool “forward_message” changed its title: Forward Message cosmetic
- Tool “get_usage” changed its title: Get Usage cosmetic
- Tool “get_verification_code” changed its title: Get Verification Code cosmetic
- Tool “get_verification_link” changed its title: Get Verification Link cosmetic
- Tool “list_inboxes” changed its title: List Inboxes cosmetic
- Tool “list_threads” changed its title: List Threads cosmetic
- Tool “read_message” changed its title: Read Message cosmetic
- Tool “read_messages” changed its title: List Messages cosmetic
- Tool “reply_to_message” changed its title: Reply to Message cosmetic
- Tool “send_email” changed its title: Send Email cosmetic
- Tool “wait_for_email” changed its title: Wait for Email cosmetic
- Tool “read_thread” changed its title: Read Thread cosmetic
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 20 Sept 2026 · Probed https://api.deadsimple.email/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.deadsimple.email | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 20 Apr 2026 | 3 Nov 2026 | RSA 2048 | SHA256-RSA | 71f8abbe728cfb410ce84e171ca8f78 |
| SANs: api.deadsimple.email, ws.deadsimple.email | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.deadsimple.email. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| email. | present | 62422 | 8 | Verified |
| deadsimple.email. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://api.deadsimple.email/.well-known/oauth-protected-resource/mcp"
Bearer resource_metadata="https://api.deadsimple.email/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| www-authenticate | Bearer resource_metadata="https://api.deadsimple.email/.well-known/oauth-protected-resource/mcp" |
Protected resource metadata
| Document | https://api.deadsimple.email/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://api.deadsimple.email/mcp |
| Authorisation server | https://api.deadsimple.email |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.deadsimple.email/mcp | Auth required | 401 | |
| http (plaintext) | http://api.deadsimple.email/mcp | HTTPS enforced |
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 →
create_inbox Create Inbox ~76
Create a new email inbox. Returns the inbox details including the email address. Args: display_name: Friendly name for the inbox (e.g. "Support Bot") tags: Comma-separated tags (e.g. "support,production")
| Name | Type | Req | Description |
|---|---|---|---|
| display_name | string | – | – |
| tags | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
delete_inbox Delete Inbox ~39
Delete an inbox and all its messages. Args: inbox_id: The inbox ID to delete
| Name | Type | Req | Description |
|---|---|---|---|
| inbox_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
forward_message Forward Message ~90
Forward a message to new recipients. Args: inbox_id: The inbox containing the message message_id: The message ID to forward to: Recipient email address (comma-separated for multiple) body: Optional additional text to include
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | – |
| inbox_id | string | yes | – |
| message_id | string | yes | – |
| to | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_usage Get Usage ~24
Get account usage metrics: inboxes, emails sent/received, plan limits.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_verification_code Get Verification Code ~119
Wait for a verification/OTP email and return the extracted code. Waits for the next new inbound email, then returns the auto-extracted verification code (and any magic link). Perfect for autonomous sign-ups. Args: inbox_id: The inbox to watch from_contains: Only match senders containing this text (optional) timeout_seconds: Max seconds to wait (default 60)
| Name | Type | Req | Description |
|---|---|---|---|
| from_contains | string | – | – |
| inbox_id | string | yes | – |
| timeout_seconds | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_verification_link Get Verification Link ~88
Wait for an email and return the extracted magic link / verification URL. Args: inbox_id: The inbox to watch from_contains: Only match senders containing this text (optional) timeout_seconds: Max seconds to wait (default 60)
| Name | Type | Req | Description |
|---|---|---|---|
| from_contains | string | – | – |
| inbox_id | string | yes | – |
| timeout_seconds | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_inboxes List Inboxes ~44
List all email inboxes in the account. Args: limit: Maximum number of inboxes to return (default 20)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_threads List Threads ~59
List conversation threads in an inbox. Args: inbox_id: The inbox to list threads for limit: Maximum number of threads to return (default 10)
| Name | Type | Req | Description |
|---|---|---|---|
| inbox_id | string | yes | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
read_message Read Message ~57
Read a single message with full body content. Args: inbox_id: The inbox containing the message message_id: The message ID to read
| Name | Type | Req | Description |
|---|---|---|---|
| inbox_id | string | yes | – |
| message_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
read_messages List Messages ~58
Read recent messages in an inbox. Args: inbox_id: The inbox to read from limit: Maximum number of messages to return (default 10)
| Name | Type | Req | Description |
|---|---|---|---|
| inbox_id | string | yes | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
read_thread Read Thread ~56
Read all messages in a conversation thread. Args: inbox_id: The inbox containing the thread thread_id: The thread ID to read
| Name | Type | Req | Description |
|---|---|---|---|
| inbox_id | string | yes | – |
| thread_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
reply_to_message Reply to Message ~78
Reply to a message. Threading headers are set automatically. Args: inbox_id: The inbox containing the message message_id: The message ID to reply to body: Reply body (plain text)
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| inbox_id | string | yes | – |
| message_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
send_email Send Email ~125
Send an email from an inbox. Args: inbox_id: The inbox to send from to: Recipient email address (comma-separated for multiple) subject: Email subject line body: Email body (plain text) cc: CC recipients (comma-separated, optional) bcc: BCC recipients (comma-separated, optional)
| Name | Type | Req | Description |
|---|---|---|---|
| bcc | string | – | – |
| body | string | yes | – |
| cc | string | – | – |
| inbox_id | string | yes | – |
| subject | string | yes | – |
| to | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
wait_for_email Wait for Email ~141
Block until a NEW inbound email arrives in the inbox, then return it. Use for signup/verification flows: trigger the action that sends the email, then call this to receive it. Only emails arriving after this call count. Args: inbox_id: The inbox to watch from_contains: Only match senders containing this text (optional) subject_contains: Only match subjects containing this text (optional) timeout_seconds: Max seconds to wait (default 60)
| Name | Type | Req | Description |
|---|---|---|---|
| from_contains | string | – | – |
| inbox_id | string | yes | – |
| subject_contains | string | – | – |
| timeout_seconds | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the Dead Simple Email MCP server?
Dead Simple Email is an MCP server listed in the public MCP registry as email.deadsimple/dead-simple-email. Give an agent its own inbox: send, receive, and pull signup codes from real email. This page covers its hosted endpoint (https://api.deadsimple.email/mcp).
Is the Dead Simple Email MCP server safe to use?
Dead Simple Email scores 36 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 Dead Simple Email MCP server expose?
Dead Simple Email exposes 14 tools: create_inbox, list_inboxes, delete_inbox, send_email, read_messages, and 9 more. Their descriptions and schemas cost roughly 1,054 tokens of context every time the server is loaded.
Does the Dead Simple Email MCP server require authentication?
Yes. Dead Simple Email asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Dead Simple Email MCP server still maintained?
Dead Simple Email is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.