useblip/email
Related Servers
Alternatives to useblip/email
- AlicenseBqualityCmaintenance🚀 Active Fork of executeautomation/mcp-playwright This repository is an actively maintained continuation of the original MCP Playwright server: >👉 https://github.com/executeautomation/mcp-playwright A Model Context Protocol server that provides browser automation capabilities using Playwright.63211,800 npm1MIT
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
- AlicenseNot gradedqualityCmaintenanceDisposable email for humans and AI agents. Enables AI agents to create mailboxes and receive verification emails through an MCP server.36MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that gives AI agents disposable email addresses and real phone numbers with automatic OTP extraction and self-destructing identities.MIT
- 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
- AlicenseAqualityAmaintenanceEnables AI agents to create disposable email inboxes, read messages, and wait for verification codes (OTPs) through MCP tools.437 npmMIT
- AlicenseNot gradedqualityDmaintenanceGives AI agents a real email identity, OTP reading, autonomous signup, and MCP server registry via a single stdio MCP connection.4 npmMIT
TDQS
Scored across 7 tools
Each tool targets a distinct operation: inbox lifecycle (create, delete, list, get), email reading, waiting, and code extraction. No overlap in purpose; an agent can clearly distinguish which tool to use for a given task.
All tool names follow a consistent snake_case verb_noun pattern (e.g., create_inbox, list_inboxes, read_email, extract_codes). The naming is uniform and predictable, making it easy to understand the action and resource.
With 7 tools, the set is well-scoped for a disposable email server. Each tool provides a necessary part of the workflow (creation, management, retrieval, extraction) without bloat or excessive specialization.
The tool surface covers the full lifecycle of a disposable inbox: creation, listing, reading, waiting for emails, extracting codes, and deletion. No obvious gaps exist for the intended use case, as sending emails is not part of a disposable inbox service.