Whatsapp (vidaai) MCP Server
@vidaai/whatsapp-mcp
npm
v0.4.0
Published by @vidaai — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
WhatsApp MCP server for Claude Code — read, search, and send WhatsApp messages with E2E encryption
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 1.2 = 99. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −1.2 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
2. Client adoption risk — 99 − 5 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 2
medium Untrusted input can drive an external actionMTC-FLOW-005
Untrusted-input tools ([whatsapp_read_messages, whatsapp_unread_summary]) co-exist with external-action tools ([whatsapp_send_message]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [whatsapp_read_messages, whatsapp_unread_summary] → sinks [whatsapp_send_message]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow whatsapp_read_messages → whatsapp_send_message
low Package runs install-time scripts (postinstall)MTC-SUP-010
"@vidaai/whatsapp-mcp" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.
Evidence: node scripts/patch-baileys.cjs
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package @vidaai/whatsapp-mcp
Tools 10
Each tool and what it can reach — statically extracted from the published source.
whatsapp_read_messagesingests untrusted inputwhatsapp_send_messagenetwork egresswhatsapp_unread_summaryingests untrusted inputwhatsapp_complete_action_itemno sensitive capabilitywhatsapp_create_action_itemno sensitive capabilitywhatsapp_list_action_itemsno sensitive capabilitywhatsapp_list_conversationsno sensitive capabilitywhatsapp_searchno sensitive capabilitywhatsapp_send_fileno sensitive capabilitywhatsapp_syncno sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (10 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.4.0 latest |
A 94/100 | 2 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @vidaai/whatsapp-mcp --onlineOther implementations of Whatsapp 11
Independent packages implementing the same tool, scanned with the same engine. Compare all 12 side by side →
WhatsApp MCP Server: Human-in-the-loop for AI agents via WhatsApp for confirmations, notifications, and interactive questions.
Least-privilege, send-only MCP server for WhatsApp. Exposes two send tools (text + approved template) backed by Meta's official WhatsApp Cloud API. No reading, listing, contacts, media, or inbound handling.
MCP server for whatsapp API integration
WhatsApp MCP Server
MCP server for WhatsApp integration
Security-hardened WhatsApp MCP server built with Baileys
More in Productivity & Workflow
MCP AgentChat - 让 AI Agent 通过 Telegram 与用户实时交互：发送消息、图片，等待用户回复
A Model Context Protocol (MCP) server for Airthings Air Quality Monitor devices.
MCP server for Anki
TypeScript package for reading and searching Apple Notes on macOS via direct SQLite access. Includes markdown conversion, attachment support, and offers a local MCP server!
Verified biotech catalyst calendar (PDUFA/AdComm/trial readouts) anchored to official sources.
Appointment booking platform letting agents check provider availability and create bookings.