MCP.Market

Guarded WhatsApp MCP server

by peter-tnc-453·io.github.peter-tnc-453/guarded-whatsapp-mcp·v0.1.0
No reviews yet

Security gate for agent-driven WhatsApp: allowlist, secret scan, rate limit, audit log.

A85/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A85/100

full report

Adoption
New

0 stars19 downloads/wk

Reviews

Write one

Nobody has reviewed Guarded WhatsApp yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Guarded WhatsApp tools (5, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • wa_audit_tail

    Return the most recent send-attempt audit records (allowed, blocked, or failed). Read-only. Message bodies are stored as a short preview + hash only.

  • wa_list_recipients

    List the allowlisted WhatsApp recipients this engine is permitted to message. Read-only. Numbers are masked. Use the returned `name` as the `recipient` argument to wa_preview / wa_send_message / wa_send_file.

  • wa_preview

    Dry-run a send: run every security check and report exactly what WOULD happen, WITHOUT sending. Returns a verdict and, when the send needs confirmation, a `confirm_token` to pass back to the send tool. Use this before any send you are unsure about.

  • wa_send_filewrite action

    Send a file to an allowlisted recipient. The filename is auto-sanitized to an ASCII-safe name (so WhatsApp shows a real name, not 'Untitled', and no path traversal is possible), the type/size are validated, and the caption is secret-scanned. Sending files may require a confirm_token (see wa_preview).

  • wa_send_messagewrite action

    Send a WhatsApp text message to an allowlisted recipient. Passes through the full security gate (allowlist, secret scan, rate limit, confirmation). If the result has needs_confirm=true, re-call with the returned confirm_token.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan11 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 89 days ago12/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Guarded WhatsApp compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 73% of 4,464 AI and agents servers
Tools
5
the typical AI and agents server has 6
Tools that change things
40%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
19
more than 5% of 1,515 AI and agents servers with a package

What its tools let an agent do: 3 read · 2 change

Install Guarded WhatsApp in Claude Code, Cursor or VS Code

claude mcp add guarded-whatsapp-mcp -- uvx guarded-whatsapp-mcp
Add to Cursor

What the publisher says

From the Guarded WhatsApp repository's README, as published. We do not edit it. Read it on GitHub

guarded-whatsapp-mcp

Govern & automate WhatsApp safely for AI agents.

An MCP server that lets an AI agent (or any MCP client) send WhatsApp messages and files — but only through a security gate you control: a recipient allowlist, secret scanning, file validation, rate limiting, a confirmation gate, and an append-only audit log.

Most WhatsApp bridges send anything, anywhere, with no record. That is fine for a human clicking send. It is not fine for an autonomous agent. guarded-whatsapp-mcp is the governance layer that makes agent-driven WhatsApp safe enough to trust.

This is not a Slack replacement. No channels, no threads, no workspace UI. It makes

the WhatsApp you already use safe to automate.

See it in action

Good sends go through · a leaked key and an un-allowlisted number are blocked · files need a preview · everything is logged.

How it works

⚠️ Read this first — unofficial transport & WhatsApp Terms

This server governs access to a transport; by default that transport is the unofficial whatsmeow-based bridge (e.g. whatsapp-mcp), which speaks WhatsApp Web's private protocol.

banned**. A reverse-engineered client cannot avoid this.

  • An unofficial client violates WhatsApp's Terms of Service and **can get a number

WhatsApp Business Cloud API. An official Cloud-API backend is on the roadmap; the guard layer is built to front either transport.

  • Use a secondary / non-critical number. Never your primary or business-critical one.
  • Not for production customer messaging — use the official

The guardrails here reduce operational risk (wrong recipient, leaked secret, spam). They do not change the Terms-of-Service risk of the underlying bridge. We are loud about this on purpose so you can choose with eyes open.

Why teams use it

Security controls

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Guarded WhatsApp: common questions

Is Guarded WhatsApp MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the Guarded WhatsApp safety report
How do I install Guarded WhatsApp?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Guarded WhatsApp need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Guarded WhatsApp maintained?
The last commit was 126 days ago (2026-06-29). The latest release is v0.1.0.
What can I use instead of Guarded WhatsApp?
Servers from other publishers that do the same job: Agent Security Scanner MCP server, three.ws Provenance MCP server and HOL Guard MCP server.
How does Guarded WhatsApp compare with other AI and agents MCP servers?
safety score 85/100 (higher than 73% of 4,464 AI and agents servers); tools 5 (the typical AI and agents server has 6); tools that change things 40% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Guarded WhatsApp

Same job from other publishers: the closest match first, then the best rated.

  • Agent Security Scanner
    Security layer for AI agents: blocks prompt injection, detects fake packages, scans vulnerabilities.
    C
  • three.ws Provenance
    Append-only, signed, on-chain-verifiable agent action log — record and audit what agents did.
    B
  • HOL Guard
    Local-first AI agent security evidence and approval workflows through HOL Guard's stdio MCP server.
    A
  • Godot MCP
    Agent-driven Godot playtesting: editor control, input injection, game-time stepping, live state.
    A
  • Roast My Design System
    Audit your Design System and serve your Agent the rules that keep AI-written UI on-system.
    A