Skip to main content
Glama
voidly-ai

voidmail

by voidly-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to voidmail

No user-submitted related servers found.

    Related Servers

    • AgentMail

      agentmail-to
      -
      license
      C
      quality
      C
      maintenance
      Gives on-the-fly inboxes to AI agents. Agents / LLM's can send, receive, and take action in isolated inboxes. Built for AI unlike Gmail. Check us out at agentmail.to
      10
      111
      -

    • AI Mail MCP

      hapitech
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to work with real email: add domains with exact DNS records, create mailboxes, aliases and catch-alls, read one unified inbox across them, wait for sign-up codes and magic links, then send, reply in-thread, forward and draft. Scoped tokens with a send permission and daily cap, dry runs on every write, signed webhooks and a full audit log keep agent mail controlled.
      MIT
    • AgenticMail by agenticmail

      AgenticMailofficial

      agenticmail
      A
      license
      A
      quality
      A
      maintenance
      Real email and SMS for AI agents. Run a local mail server with disposable inboxes — agents send and receive real email, fetch verification codes, and drive a real inbox without going through any third-party email API.
      100
      242
      MIT

    • zerodrop-mcp

      zerodrop-dev
      A
      license
      A
      quality
      B
      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
      199 npm
      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.6/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools target clearly distinct actions, but voidmail_send_email and voidmail_send_once overlap heavily—the description admits send_email is 'legacy' and prefers send_once, which invites misselection. Similarly, read_email implicitly marks read while mark_read exists separately, and policy vs sending_limits have related purposes.

    Naming Consistency4/5

    All tools share the voidmail_ prefix and mostly follow a verb_noun pattern (list_inbox, create_alias, send_once). A few break the pattern into bare nouns (account_info, sending_limits, policy), which is a minor deviation but not confusing.

    Tool Count3/5

    At 21 tools this sits in the heavy range for a single mailbox server. The domain is broad (accounts, aliases, inbox, sending, policy, webhooks), so most tools are justified, but the legacy send_email and multiple overlapping send/status tools inflate the count.

    Completeness4/5

    Coverage is strong across the lifecycle: account creation, alias CRUD, inbox read/search/wait, send with idempotency and status, recipient policy, webhook and stats. Minor gaps like no outbox/sent-listing or alias update are workable around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources