Skip to main content
Glama
brobin002

SandMail — Disposable Email API for AI Agents

by brobin002
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to SandMail — Disposable Email API for AI Agents

No user-submitted related servers found.

    Related Servers

    • courier-mcp

      antonioac1
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to create disposable email inboxes and automatically extract OTPs, magic links, and verification codes from incoming emails.
      10 npm
      MIT

    • zerodrop-mcp

      zerodrop-dev
      A
      license
      A
      quality
      A
      maintenance
      Provides disposable email inboxes for AI agents to automatically receive and extract OTPs and magic links, enabling seamless email verification during autonomous workflows.
      3
      86 npm
      MIT

    • UnCorreoTemporal

      francofuji
      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

    • useblip/email

      blipemail
      A
      license
      A
      quality
      C
      maintenance
      MCP server for disposable email — create inboxes, receive emails, and extract OTP codes. Let your AI agent sign up for services, wait for verification emails, and extract codes autonomously.
      7
      37 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 8 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no overlap. For example, create_inbox and delete_inbox handle inbox lifecycle, get_emails and get_otp focus on email retrieval vs. code extraction, and wait_for_email vs. wait_for_otp differentiate between general waiting and OTP-specific waiting. The descriptions reinforce these distinctions.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern (e.g., create_inbox, delete_inbox, get_emails). There are no deviations in style or convention, making the set predictable and easy to understand at a glance.

    Tool Count5/5

    With 8 tools, this server is well-scoped for its disposable email API purpose. Each tool earns its place by covering distinct aspects like inbox management, email retrieval, OTP handling, and quota checking, without being overly sparse or bloated.

    Completeness5/5

    The tool surface provides complete coverage for the disposable email domain. It includes CRUD operations for inboxes (create, list, delete), email retrieval (get_emails, wait_for_email), OTP-specific utilities (get_otp, wait_for_otp), and quota management (get_quota), with no obvious gaps for typical agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources