Skip to main content
Glama
rchanllc

joltsms-mcp-server

by rchanllc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to joltsms-mcp-server

No user-submitted related servers found.

    Related Servers

    • MCP Agents SMS

      gonchasobaka
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables AI agents to autonomously buy virtual phone numbers and receive SMS verification codes. Supports multiple providers (5sim, SMS-Activate, OnlineSim) with automatic cheapest-provider selection.
      2
      MIT

    • GetSms

      beautifulSoup
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that lets AI agents retrieve the latest SMS verification code by keyword, using self-hosted phone forwarding and persistent storage.
      19 npm
      1
      MIT
    • @saperly/mcp by Saperly

      @saperly/mcpofficial

      Saperly
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Saperly that enables AI agents to provision phone numbers, place calls, send SMS, and manage credentials via 36 tools backed by the Saperly API.
      14 npm
      3
      MIT

    • identity-mcp

      purple-flea
      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
    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 12 tools

    Disambiguation4/5

    Most tools target distinct resource+action pairs (list_numbers vs get_number vs provision_number vs release_number are clearly separated). There is mild overlap in the OTP retrieval cluster (wait_for_sms, get_latest_otp, list_messages), but the descriptions explicitly differentiate them (wait vs. latest vs. full listing), so misselection risk is low.

    Naming Consistency4/5

    All tools share a consistent 'joltsms_' prefix and follow a verb_noun pattern (list_numbers, get_number, update_number, provision_number, release_number, mark_read, wait_for_sms). The one deviation is 'billing_status', which is noun-only and lacks a verb, but this is a minor blemish in an otherwise uniform scheme.

    Tool Count5/5

    Twelve tools is well within the ideal range and each maps to a distinct, meaningful operation (number lifecycle, messaging, OTP retrieval, billing, payment methods). No obvious redundant or filler tools inflate the set.

    Completeness4/5

    The number lifecycle (list/get/update/provision/release), messaging (list/reply/mark_read/wait), OTP helpers, billing, and payment listing are all covered, giving solid CRUD coverage for the domain. Minor gaps exist—no adding payment methods, no message search/deletion—and sending to arbitrary numbers is intentionally unsupported, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources