MockPost
Related Servers
Alternatives to MockPost
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables 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
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create and use temporary email and SMS inboxes, check messages, and wait for or extract OTPs and verification links during account registration. Combines both channels through a unified OTP tool while redacting sensitive tokens in audit logs.MIT
- AlicenseAqualityDmaintenanceProgrammatic email deliverability testing for AI agents. Create inbox placement tests across Gmail, Outlook, Yahoo, Mail.ru, Yandex — get per-provider placement (Inbox/Spam/Promotions), SPF/DKIM/DMARC auth, Rspamd & SpamAssassin verdicts, DNS health (MX, PTR, DNSBL), and live SSE results.534 npm2MIT
- 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.339 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides 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.433 npmMIT
TDQS
Scored across 31 tools
Most tools have a distinct resource+action purpose, so an agent can usually select the right one. A few pairs overlap or look similar—list_webhooks vs list_webhook_deliveries, list_sent_messages vs get_timeline_markdown, and clear_channel vs clear_all—but the descriptions clarify the boundaries.
All tool names use snake_case with a verb-first pattern such as list_, get_, set_, register_, simulate_, and clear_. Minor multiword names like simulate_push_token_unregistered remain readable and do not break the overall convention.
31 tools is above the 25-tool threshold where the surface starts to feel heavy. The broad multi-channel domain justifies some size, but many simulate_* and channel-specific tools could be grouped or split into focused sub-servers to reduce cognitive load.
The tool set covers the core lifecycle well: app registration, webhooks, captured messages, OTP/TOTP, push subscriptions, OAuth sessions, simulation, and cleanup. Notable gaps exist, such as no delete/unregister webhook and limited inbound simulation channels beyond Telegram/WhatsApp, but typical verification workflows are still supported.