Skip to main content
Glama

Related Servers

Alternatives to useblip/email

  • A
    license
    B
    quality
    C
    maintenance
    🚀 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.
    32
    14,310 npm
    1
    MIT

Related Servers

  • A
    license
    B
    quality
    C
    maintenance
    Disposable 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.
    6
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Disposable email for humans and AI agents. Enables AI agents to create mailboxes and receive verification emails through an MCP server.
    37
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    MCP server that gives AI agents disposable email addresses and real phone numbers with automatic OTP extraction and self-destructing identities.
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Provides 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 npm
    1
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    Enables AI agents to create disposable email inboxes, read messages, and wait for verification codes (OTPs) through MCP tools.
    4
    20 npm
    1
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Gives AI agents a real email identity, OTP reading, autonomous signup, and MCP server registry via a single stdio MCP connection.
    8 npm
    MIT

TDQS

A3.9/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a distinct resource/action: create/delete/get/list operate on inboxes, while read_email, extract_codes, and wait_for_email operate at the email level with clearly differentiated purposes. Descriptions make the granularity boundaries (inbox-level listing vs. email-level reading vs. OTP extraction) explicit enough to avoid misselection.

Naming Consistency5/5

All seven tools follow a consistent snake_case verb_noun pattern (create_inbox, delete_inbox, get_inbox, list_inboxes, read_email, wait_for_email, extract_codes). No deviations in casing or verb style.

Tool Count5/5

Seven tools is well-scoped for a disposable email server, with each tool earning its place across the create/list/read/wait/extract/delete lifecycle. Nothing feels padded or redundant.

Completeness4/5

The surface covers the core lifecycle: create, list, get, delete inboxes, plus read, wait, and OTP extraction. Minor gaps exist (e.g., no delete_email, search, or forward, and no explicit attachment handling beyond read_email), but core workflows are fully supported.

Maintenance

ActivityMaintained
ResponsivenessNo issues