Skip to main content
Glama
BACH-AI-Tools

bach-whatsapp_number_validators

by BACH-AI-Tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to bach-whatsapp_number_validators

No user-submitted related servers found.

    Related Servers

    • whatsapp-business-mcp

      Gonzalez8
      A
      license
      A
      quality
      D
      maintenance
      MCP server for the WhatsApp Business API that enables managing business accounts, phone numbers, message templates, sending template messages, and tracking message status via the Meta Graph API.
      8
      8 npm
      MIT
    • lingtai-whatsapp by Lingtai-AI

      lingtai-whatsappofficial

      Lingtai-AI
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for interacting with the official Meta WhatsApp Business Platform/Cloud API, enabling sending messages, managing contacts, templates, and handling webhook callbacks.
      Apache 2.0

    • WhatsApp Business API MCP

      ag2-mcp-servers
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP (Multi-Agent Conversation Protocol) Server that enables interaction with the WhatsApp Business API, allowing agents to send messages, manage media, and perform other WhatsApp business operations through natural language.
      1
      -

    • whats-mcp

      SaptodeepSarkar
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that turns WhatsApp into agent-callable tools, enabling search contacts, send/receive messages, read chats, handle media, and monitor calls via the WhatsApp Web multi-device protocol.
      3 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

    C2.6/5.0

    Scored across 8 tools

    Disambiguation2/5

    Multiple tools have overlapping purposes with unclear boundaries. For example, check_if_number_is_business_via_get_request, check_if_number_is_business_via_post_request, validate_single_number_via_get_request, and validate_single_number_via_post_request all appear to perform the same WhatsApp Business verification, differing only by HTTP method. This creates significant ambiguity and potential for misselection by an agent.

    Naming Consistency2/5

    Naming conventions are inconsistent and chaotic. Tools mix descriptive names (bulk_validation, phone_number_validation_via_get_request) with vague ones (ping), and there is no consistent pattern. Some tools use snake_case with HTTP method suffixes, while others do not, leading to a lack of predictability across the set.

    Tool Count3/5

    With 8 tools, the count is reasonable for a validation server, but it feels borderline due to redundancy. The number of tools is inflated by multiple versions of the same functionality (e.g., GET vs. POST for similar checks), which could have been consolidated, making the set feel slightly heavy for its scope.

    Completeness4/5

    The tool set covers the core domain of WhatsApp number validation well, including bulk and single validations, business checks, and general phone number validation. However, there are minor gaps, such as no tools for managing validation results or handling errors explicitly, but agents can likely work around these with the provided tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources