Dead Simple Email
OCI · GHCR.IO/DEADSIMPLE-EMAIL/DEADSIMPLE-EMAIL · 3 COMPONENTS
Give an agent its own inbox: send, receive, and pull signup codes from real email.
Last scanned (21 hours ago)
Scores higher than 56% of OCI servers
Category Communication
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 79 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- 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 Management17
- Stability observed for 5 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 17 Oct 26 +2
- Stability: unverified → 0.13 ▲ functional
- 13 Oct 26 +30
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 0 functional
- First check of Destructive annotations: 100 functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: pass functional
- 10 Oct 26 9
First indexed and scored.
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 18 Oct 2026 · Analysed oci/ghcr.io/deadsimple-email/deadsimple-email@0.2.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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.
How do I install the Dead Simple Email MCP server?
Dead Simple Email runs locally as a container image, launched with docker run --rm -i -e DSE_API_KEY ghcr.io/deadsimple-email/deadsimple-email:0.2.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/deadsimple-email/deadsimple-email
claude mcp add email-deadsimple-dead-simple-email -- docker run --rm -i -e DSE_API_KEY ghcr.io/deadsimple-email/deadsimple-email:0.2.2
This image reads DSE_API_KEY. Set it in your client's env block for this server; docker run -e passes it through to the container.
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 container image (ghcr.io/deadsimple-email/deadsimple-email).
Is the Dead Simple Email MCP server safe to use?
Dead Simple Email scores 41 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.
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 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Dead Simple Email MCP server under?
Dead Simple Email declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.