Skip to main content
Glama

Related Servers

Alternatives to otpkit

No user-submitted related servers found.

    Related Servers

    • 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.
      11 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to create disposable email inboxes, read messages, and wait for verification codes (OTPs) through MCP tools.
      4
      15 npm
      1
      MIT
    • 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
      B
      maintenance
      Disposable email for humans and AI agents. Enables AI agents to create mailboxes and receive verification emails through an MCP server.
      39
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to create disposable email inboxes and automatically extract OTPs, magic links, and verification codes from incoming emails.
      10 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools are clearly partitioned by channel (temp email, free SMS, paid SMS) and action (create, list, check, wait, buy). check_email vs wait_for_email and read_free_sms vs wait_for_sms could be momentarily confused, but descriptions clearly distinguish one-shot reads from polling.

    Naming Consistency4/5

    Nearly all tools follow a verb_noun snake_case pattern (create_temp_email, read_free_sms, buy_temp_number). Minor inconsistency: the object is sometimes 'temp_email' and sometimes just 'email', and free/paid qualifiers are applied inconsistently, but the pattern remains readable.

    Tool Count5/5

    11 tools is well within the ideal 3-15 range and each maps to a distinct step in the OTP acquisition workflow. No obviously redundant or filler tools.

    Completeness4/5

    The surface covers the full lifecycle of receiving OTPs via email and SMS, plus a standalone extraction utility. Minor gaps: no deletion/cleanup of temp addresses, no listing of existing paid orders/numbers, and no provider configuration setter (only get_sms_providers status).

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues