MCP server · Audited from source
WhatsApp MCP server
by lharries/whatsapp-mcpMIT licenceAudited 21 Sep 2026 · source b3c2312ef81a
Is it safe? Yes — SAFE, grade B (89/100). It exposes 12 tools: 9 read, 3 write and 0 destructive. The audit recorded 2 findings (0 critical, 0 high, 0 medium, 1 low). Maintainer's description: WhatsApp MCP server
Cite
Cite this page
ModelsAtlas. “WhatsApp MCP server (lharries/whatsapp-mcp)”. Retrieved 21 Sep 2026. https://modelsatlas.com/mcp/lharries/whatsapp-3
5 MCP servers are called WhatsApp. You are viewing lharries/whatsapp-mcp. Compare all 5 →
- verygoodplugins/whatsapp-mcp Org-owned★ 220!CAUTION
- lharries/whatsapp-mcp★ 6,292✓SAFE
- jlucaso1/whatsapp-mcp-ts★ 74✓SAFE
- msaelices/whatsapp-mcp-server★ 27✓SAFE
Trust audit
Audit 0.4.1 · full source read 21 Sep 2026
2 findings, listed below with the file and line each was found on. Grade A needs a sandboxed behavioural run too; this audit read the source only.
What the source does
- FilesystemNone observedNothing seen in the source
- NetworkDeclared5 observations
- ShellNone observedNothing seen in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
“Declared” means the server says it does this and the source agrees. Browser, file and shell access are expected of some kinds of server.
Five audit layers
| Layer | What we check | Result |
|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS 1 finding |
L1 Static source | Secrets, path traversal, supply chain | PASS |
L2 Instructions | Prompt injection and authority framing in docs and tool descriptions | PASS 1 finding |
L3 Inventory | Declared tools match the source | PASS |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED |
Provenance & runtime
Who published it, and what the audit could and could not run
Provenance
- Repository owner
lharriesUser accountAccount type recorded when we read the repository. - PackagePublished on PyPI
whatsapp-mcp-server, no version recorded - LicenceMITFrom the repository, as read at the audited commit.
- Last push14 months agoActivity of the repository when we read it.
- Source commit readb3c2312ef81aThe audit covers exactly this commit, read on 21 Sep 2026.
Runtime
- Sandbox runNot run yetThis audit read the source only; it did not execute the server.
- Tool inventory12 declaredRead from the source and classed read, write or destructive.
Every value here is read from the record's own repository and audit.Suggest a correction
Findings (2)
Sorted by severity
LOWSupply chainprompt.pipe_to_shell · README.md:24
- UV (Python package manager), install with `curl -LsSf https://astral.sh/uv/install.sh | sh`
- Why
- No further detail recorded for this rule.
- Fix
- —
INFOInventory / provenanceinv.oversize · example-use.png
example-use.png
- Why
- 3149200 bytes not read
- Fix
- —
Tools it exposes
12 declared in source · 0 destructive
| Tool | Risk | What it does |
|---|---|---|
send_audio_message | write | Send any audio file as a WhatsApp audio message to the specified recipient. For group messages use the JID. If it errors due to ffmpeg not being installed, use send_file instead. |
send_file | write | Send a file such as a picture, raw audio, video or document via WhatsApp to the specified recipient. For group messages use the JID. |
send_message | write | Send a WhatsApp message to a person or group. For group chats use the JID. |
download_media | read | Download media from a WhatsApp message and get the local file path. |
get_chat | read | Get WhatsApp chat metadata by JID. |
get_contact_chats | read | Get all WhatsApp chats involving the contact. |
get_direct_chat_by_contact | read | Get WhatsApp chat metadata by sender phone number. |
get_last_interaction | read | Get most recent WhatsApp message involving the contact. |
get_message_context | read | Get context around a specific WhatsApp message. |
list_chats | read | Get WhatsApp chats matching specified criteria. |
list_messages | read | Get WhatsApp messages matching specified criteria with optional context. |
search_contacts | read | Search WhatsApp contacts by name or phone number. |
Install
audited commit b3c2312
One-click links open your editor with the config below filled in, exactly as the snippets show it. The audit covers commit b3c2312 only.
claude mcp add whatsapp-mcp-server -- uvx whatsapp-mcp-server
{
"mcpServers": {
"whatsapp-mcp-server": {
"command": "uvx",
"args": [
"whatsapp-mcp-server"
]
}
}
}The command does not pin a version; the audit covers commit b3c2312ef81a. Transport: stdio. No environment variables required.
Audit history
- ✓SAFE B 89 / 100
Source changed, verdict held ·
b3c2312ef81a
README badge
For maintainers · updates on every re-audit
[](https://modelsatlas.com/mcp/lharries/whatsapp-3/)
The badge always shows the latest audit; a maintainer cannot pin an old verdict.
Other ratings
Cited, never blended into our score
No third-party security ratings are recorded for this server yet. When they exist they appear here with their source and date, beside, not inside, our grade.
Questions about WhatsApp MCP server
What is the WhatsApp MCP server?
What tools does WhatsApp expose?
Is WhatsApp safe to connect to an agent?
What credentials does WhatsApp need?
How does WhatsApp run?
How current is this page?
Which WhatsApp MCP server is the right one?
Sources
- lharries/whatsapp-mcp on GitHub — the source we read, its licence, stars and activityObserved · 21 Sep 2026
- ModelsAtlas trust audit — SAFE verdict for commit b3c2312ef81aObserved · 21 Sep 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What is the WhatsApp MCP server?
- What tools does WhatsApp expose?
- Is WhatsApp safe to connect to an agent?