tmailor-mcp
OfficialRelated Servers
Alternatives to tmailor-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceEnables AI agents to create temporary email addresses, receive confirmation emails, and extract verification links, automating sign-up and email verification workflows without manual intervention.627 npm62MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to generate temporary email addresses, receive emails, and automatically extract OTP codes and links from incoming messages for automation and testing workflows.MIT

Mailsac MCP Serverofficial
AlicenseAqualityCmaintenanceEnables AI coding agents to create disposable test inboxes, wait for and read incoming email, and extract confirmation links and one-time codes for sign-up, password-reset, and magic-link flows.615 npmMIT- AlicenseNot gradedqualityBmaintenanceProvides temporary email inboxes for AI agents, enabling creation, inspection, and deletion of inboxes, retrieval of messages, and extraction of OTPs and verification links via MCP tools.23 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create disposable email inboxes and automatically extract OTPs, magic links, and verification codes from incoming emails.14 npmMIT
- AlicenseAqualityAmaintenanceEnables AI agents to create disposable email inboxes, read messages, and wait for verification codes (OTPs) through MCP tools.420 npm1MIT
TDQS
Scored across 8 tools
Each tool targets a distinct resource and action: mailbox lifecycle (create/list/delete), message retrieval (wait/list/read), domains, and account status. The only near-overlap is wait_for_message vs read_message, but the descriptions clearly separate waiting-for-new-unread from reading a specific message.
Almost all names follow a verb_noun pattern (create_mailbox, delete_mailbox, list_messages, read_message, etc.), which is predictable and readable. account_status is the one deviation, breaking the verb-first convention, but it is a minor, understandable exception.
Eight tools is well-scoped for a temporary-email service, with each tool earning its place across mailbox management, message handling, and account/domain introspection. No redundant or filler tools.
The full lifecycle is covered: create/delete/list mailboxes, plus list/read/wait for messages, with domains and account status for context. There are no obvious dead ends for the core receive-temporary-mail purpose.