best-tempmail-mcp
Related Servers
Alternatives to best-tempmail-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create disposable email inboxes and automatically extract OTPs, magic links, and verification codes from incoming emails.8 npmMIT
- AlicenseAqualityAmaintenanceProvides disposable email inboxes for AI agents to automatically receive and extract OTPs and magic links, enabling seamless email verification during autonomous workflows.353 npmMIT
- 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.621 npm61MIT
- AlicenseAqualityCmaintenanceProvides AI agents with real email infrastructure, enabling them to create inboxes, send/receive messages, and extract verification codes from incoming mail.14MIT
- AlicenseAqualityBmaintenanceProvides temporary email services for AI agents, enabling closed-loop verification of email-based registration flows with multi-provider support, auto-registration, and verification code extraction.1013 npmMIT
- AlicenseNot gradedqualityCmaintenanceDisposable email for humans and AI agents. Enables AI agents to create mailboxes and receive verification emails through an MCP server.36MIT
TDQS
Scored across 7 tools
Each tool targets a distinct stage of the temporary-email workflow: create inbox, list mail, wait for mail, read a message, extract a code, list domains, and delete inbox. Close pairs like list_messages/wait_for_email and read_message/get_verification_code are explicitly differentiated in their descriptions.
All tool names use a consistent snake_case, verb-first convention: create_inbox, list_messages, read_message, delete_inbox, wait_for_email, and get_verification_code. The phrasal wait_for_email still fits the predictable pattern.
Seven tools provide a well-scoped set for a focused temporary-email server. Each tool has a clear role and none feels redundant, while the count stays comfortably within the ideal range.
The surface covers the full temporary-email lifecycle: create an inbox, optionally choose a domain, wait for or list incoming messages, read message content, extract verification codes, and delete the inbox. No significant workflow gap is apparent for a receive-only temp-email service.