mailflat-mcp
OfficialRelated Servers
Alternatives to mailflat-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceDisposable email MCP server for autonomous AI agents. Create labeled temporary inboxes, wait for verification emails, extract OTP codes and confirmation links — zero human intervention required.6MIT
- AlicenseAqualityBmaintenanceMCP server that gives an AI agent a throwaway test identity — a real disposable email address and a real UK phone number — so it can sign up for something it's testing and read back the verification email/SMS itself, without a human in the loop.544 npmMIT
- AlicenseAqualityCmaintenanceMCP server for disposable email — create inboxes, receive emails, and extract OTP codes. Let your AI agent sign up for services, wait for verification emails, and extract codes autonomously.737 npm1MIT
- AlicenseNot gradedqualityBmaintenanceOpen-source, self-hosted Inbox-as-a-Service API for AI agents. It enables agents to manage email inboxes, send/receive emails, search messages, and wait for replies via REST or MCP.27Apache 2.0
- AlicenseAqualityCmaintenanceMCP server for disposable email. Gives an assistant its own throwaway inbox, then hands back the confirmation code out of the message that arrives.511 npmMIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that provides AI agents with a persistent, agent-native email mailbox for sending, receiving, and managing emails through bounded-context retrieval, idempotent operations, and explicit acknowledgement.MIT
TDQS
Scored across 12 tools
Each tool maps to a distinct operation: inbox lifecycle, message reading/waiting, sending/replies, delivery status, and cleanup. Similar tools like wait_for_message and wait_for_otp are separated by whether a parsed OTP is required, and send_email vs reply is explicitly differentiated.
Most tools follow a clear verb_noun snake_case pattern such as create_inbox, read_messages, send_email, and delete_inbox. Minor deviations like reply and wait_until_sent break the strict pattern slightly but remain readable and predictable.
12 tools is well-scoped for an email testing domain. Each tool covers a necessary workflow step—inbox management, message retrieval, polling, sending, replying, and cleanup—without redundant duplicates.
The tool set covers the full lifecycle: create/list/delete inboxes, read/wait for messages and OTPs, send and reply, check delivery status, and clean up messages. This is sufficient for common disposable-email and testing workflows with no obvious dead ends.