Skip to main content
Glama
mohamed-khairy-5i

tossinbox

by mohamed-khairy-5i
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to tossinbox

No user-submitted related servers found.

    Related Servers

    • agent-temp-mail

      ryanshahine
      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.
      205 npm
      MIT

    • smails

      pexni
      A
      license
      Not graded
      quality
      C
      maintenance
      Disposable email for humans and AI agents. Enables AI agents to create mailboxes and receive verification emails through an MCP server.
      36
      MIT

    • 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

    • agent-inbox

      gsd-build
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to create temporary email addresses, receive confirmation emails, and extract verification links, automating sign-up and email verification workflows without manual intervention.
      6
      23 npm
      63
      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
      40 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

    A4.1/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: create, list, read, and wait-for-code. There is no functional overlap between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: create_inbox, list_messages, read_message, wait_for_code. The naming is uniform and predictable.

    Tool Count5/5

    Four tools is an ideal size for a disposable inbox service. Each tool covers a necessary step in the workflow without redundancy or bloat.

    Completeness4/5

    The core lifecycle is well covered: creation, listing, reading, and polling for codes. A minor gap is the lack of an explicit delete_inbox or get_inbox, but these are not essential for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources