Dead Simple Email
Server Details
Give an agent its own inbox: send, receive, and pull signup codes from real email.
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 8.1% over 42 days
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- deadsimple-email/deadsimple-email
- GitHub Stars
- 0
- Server Listing
- email.deadsimple/dead-simple-email
TDQS
Scored across 14 tools
Each tool has a clear, distinct purpose. While wait_for_email, get_verification_code, and get_verification_link are similar, they target different use cases (generic email waiting vs. specific extraction), and the descriptions clarify their roles.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_inbox, send_email, list_threads). No mixing of conventions or vague verbs.
14 tools is well-scoped for an email server. It covers inbox management, message operations, and verification flows without being overwhelming or sparse.
Covers essential CRUD for inboxes and messages (create/delete/list inbox, send/reply/forward/read messages). Missing message deletion and inbox update, but the core workflow is solid.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
14 tool updates
- First observed
create_inbox - First observed
delete_inbox - First observed
forward_message - First observed
get_usage - First observed
get_verification_code - First observed
get_verification_link - First observed
list_inboxes - First observed
list_threads - First observed
read_message - First observed
read_messages - First observed
read_thread - First observed
reply_to_message - First observed
send_email - First observed
wait_for_email
Related MCP Connectors
Give an AI agent its own email address: send, reply, read, and wait for mail.
Give an AI agent its own inbox — receive email as a webhook, send over a verified domain.
Email inboxes for AI agents: send, receive, reply, search, and manage threaded email over MCP.
Real email inboxes for AI agents: create addresses, send, wait for mail and verification codes.
Related MCP Servers
AlicenseAqualityAmaintenanceMCP server that gives an agent its own email inbox: it opens the inbox, waits for the one-time code a signup sends, and reads or sends mail. Addresses are permanent, so a test suite does not need a new one per run; only the messages expire, on a retention window you set.12MIT- FlicenseNot gradedqualityDmaintenanceGive AI agents their own email inboxes. Create, send, receive, and manage email entirely via MCP tools.-

InboxAPI CLIofficial
AlicenseNot gradedqualityBmaintenanceProvides an AI agent with its own email address to send, receive, and manage emails via MCP. No email server setup required.19 npm12MIT
AgenticMailofficial
AlicenseAqualityAmaintenanceReal email and SMS for AI agents. Run a local mail server with disposable inboxes — agents send and receive real email, fetch verification codes, and drive a real inbox without going through any third-party email API.100225MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.