Skip to main content
Glama
peter-tnc-453

guarded-whatsapp-mcp

by peter-tnc-453
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to guarded-whatsapp-mcp

No user-submitted related servers found.

    Related Servers

    • Meta Business MCP

      metabusiness-mcp
      F
      license
      Not graded
      quality
      D
      maintenance
      Compliance intelligence layer for AI agents sending WhatsApp Business messages. Prevents account suspensions by validating Meta's rules (care windows, opt-outs, rate limits) in real-time before every send.
      1
      -

    • WhatsApp MCP Server

      Malaccamaxgit
      A
      license
      Not graded
      quality
      C
      maintenance
      Integrates WhatsApp with AI agents, enabling message sending, chat search, media sharing, approval workflows, and activity summaries via any MCP client.
      1
      Apache 2.0

    • whatsapp-mcp-server

      FredShred7
      A
      license
      A
      quality
      D
      maintenance
      Connects AI assistants to the official Meta WhatsApp Cloud API for managing conversations and sending various message types through natural language. It provides tools for media management, template messages, and real-time webhook processing without the risk of account bans.
      18
      6 npm
      23
      MIT

    • zaileys-mcp

      zeative
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to control WhatsApp, including sending messages and media, reading chats, managing groups and communities, with QR/pairing auth and session persistence.
      14
      19 npm
      2
      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

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing recipients, dry-running a send, viewing audit records, sending messages, and sending files. The preview tool is explicitly read-only, so there is no confusion with the actual send tools.

    Naming Consistency4/5

    All tools share the wa_ prefix and use snake_case with verb-oriented names like wa_list_recipients and wa_send_message. wa_preview is a minor deviation because it lacks a noun object, and wa_audit_tail is slightly awkward, but the overall pattern is predictable.

    Tool Count5/5

    Five tools is well-scoped for a guarded WhatsApp messaging server: recipient discovery, preview/checking, audit history, text sending, and file sending. Each tool fills a necessary role with no redundancy.

    Completeness5/5

    The core secure-send lifecycle is fully covered: identify allowed recipients, preview outcomes, send text or files, and review audit records. The confirmation flow is built into the send tools, so there are no dead ends, and external allowlist management appears intentionally out of scope.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources