Dead Simple Email

REMOTE · API.DEADSIMPLE.EMAIL · 3 COMPONENTS · SCANNED AUG 3

Give an agent its own inbox: send, receive, and pull signup codes from real email.

Available components

remote · api.deadsimple.email 64 oci · ghcr.io/deadsimple-email/deadsimple-email:0.2.2 37 pypi · deadsimple-email 24

+5 this week 64 64 Trust /100

Recent critical change

Authorization (30 Jul 2026). See the changelog before you install this server.

Trust breakdown (6 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 →

Endpoint Security57

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_inbox). See how to fix → View diagnostics → Fail
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

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability77

AI-judged instruction clarity (excellent).Pass
Tool/resource definitions use about 1112 tokens (~79/item across 14 items; 14 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management23

Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage71

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
0% of tool parameters carry a description.Fail
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · api.deadsimple.email

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http email-deadsimple-dead-simple-email https://api.deadsimple.email/mcp

# ~/.codex/config.toml

[mcp_servers.email-deadsimple-dead-simple-email]
url = "https://api.deadsimple.email/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "email-deadsimple-dead-simple-email": {
      "type": "remote",
      "url": "https://api.deadsimple.email/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add email-deadsimple-dead-simple-email --url https://api.deadsimple.email/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  email-deadsimple-dead-simple-email:
    url: "https://api.deadsimple.email/mcp"

// mcp.json

{
  "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.

Changelog Show cosmetic changes

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.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
1 Aug 26 +1
- 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 +1
- 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 “read_thread” changed its title: Read Thread 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 “delete_inbox” changed its title: Delete Inbox cosmetic
- Tool “create_inbox” changed its title: Create Inbox cosmetic
- Tool “get_verification_code” changed its title: Get Verification Code cosmetic
- Tool “get_usage” changed its title: Get Usage cosmetic
- Tool “forward_message” changed its title: Forward Message cosmetic
- Tool “read_message” changed its title: Read Message cosmetic
- Tool “list_threads” changed its title: List Threads cosmetic
- Tool “read_messages” changed its title: List Messages cosmetic
- Tool “get_verification_link” changed its title: Get Verification Link cosmetic
- Tool “list_inboxes” changed its title: List Inboxes cosmetic
29 Jul 26 +2
- Stability: unverified → 0.07 ▲ functional
27 Jul 26 59

First indexed and scored.

Show 4 earlier entries Hide earlier entries

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 3 Aug 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

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

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://api.deadsimple.email/mcp	Verified	200
http (plaintext)	http://api.deadsimple.email/mcp	HTTPS enforced

MCP tools — 14 exposed · ~1,054 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.

Tool Tokens

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

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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 Output Examples

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)

Input Output Examples

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)

Input Output Examples

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)

Input Output Examples

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)

Input Output Examples

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

Input Output Examples

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)

Input Output Examples

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

Input Output Examples

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)

Input Output Examples

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)

Input Output Examples

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)

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug