Skip to main content
Glama
CTMJSON

ctm-number-provisioner

Official
by CTMJSON
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ctm-number-provisioner

No user-submitted related servers found.

    Related Servers

    • VirtualSMS MCP Server by VirtualSMSLabs

      VirtualSMS MCP Serverofficial

      VirtualSMSLabs
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to purchase virtual phone numbers, retrieve SMS verification codes, and manage activations through natural language by wrapping the VirtualSMS Consumer API.
      9 npm
      MIT

    • Telique MCP

      Ringer
      A
      license
      A
      quality
      B
      maintenance
      Enables querying telecom routing data (LRN, CNAM, DNO, LERG, toll-free routing) directly from AI assistants like Claude, ChatGPT.
      14
      71 npm
      MIT
    • Telnyx MCP Server by team-telnyx

      Telnyx MCP Serverofficial

      team-telnyx
      F
      license
      B
      quality
      F
      maintenance
      Enables interaction with Telnyx's telephony, messaging, and AI assistant APIs to manage phone numbers, send messages, make calls, and create AI assistants. Includes webhook support for real-time event handling and comprehensive tools for voice, SMS, cloud storage, and embeddings.
      46
      25
      -

    • TelePath PSTN MCP

      ZhipingYang
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to control PSTN phone calls via TelePath, including dialing, hangup, and phone number management.
      1
      4 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.8/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool addresses a distinct stage of the number lifecycle: identity (whoami), discovery (search_available_numbers), acquisition (buy_numbers), routing options (list_routing_targets), configuration (configure_numbers), and removal (release_numbers). There is no meaningful overlap between tool purposes.

    Naming Consistency4/5

    Most tools follow a clear verb_noun snake_case pattern (search_available_numbers, buy_numbers, list_routing_targets, configure_numbers, release_numbers). The lone exception is 'whoami', a standard Unix-style command name, which is a minor deviation rather than a systemic inconsistency.

    Tool Count5/5

    Six tools provide a focused, well-scoped surface for a number-provisioning server. Each tool corresponds to a necessary step in the purchase-to-configuration workflow, and none feels redundant or extraneous.

    Completeness3/5

    The lifecycle is well covered from search/buy through configure/release, but there is no tool to list or inspect already-owned/configured numbers. This is a notable gap for agents needing to manage existing inventory, though the core provisioning flow can still be completed.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources