Skip to main content
Glama
GrizzlySMS-Git

Grizzly SMS MCP Server

Official
by GrizzlySMS-Git
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Grizzly SMS 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.
      1
      MIT

    • smspm-mcp

      alesav
      A
      license
      B
      quality
      B
      maintenance
      MCP server for sending SMS via the SMSPM API. Send transactional SMS from Claude Desktop, Cursor, Windsurf, Cline, or any MCP client.
      1
      20 npm
      MIT
    • Quackr MCP Server by quackr-mcp

      Quackr MCP Serverofficial

      quackr-mcp
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Quackr, enabling virtual phone number management including balance checking, pricing, inventory, purchasing numbers, and reading SMS via Claude or any MCP-compatible client.
      25 npm
      MIT

    • joltsms-mcp-server

      rchanllc
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for provisioning dedicated real-SIM US phone numbers, receiving inbound SMS, and extracting OTP codes. Built for AI agents automating phone verification workflows.
      17 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.7/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of the SMS verification workflow: account finances, number requests, status management, and reference data. There is no meaningful overlap between any pair of tools.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_balance, request_number). The naming is uniform and predictable across the entire set.

    Tool Count5/5

    With 8 tools, the server is well-scoped for an SMS verification service. Every tool serves a clear function without unnecessary bloat or missing essentials.

    Completeness5/5

    The tools cover the core lifecycle: top-up (get_wallet, get_balance), request a number (request_number), poll for SMS (get_status, set_status), and reference data (get_prices, get_countries, get_services). This appears sufficient for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources