Skills/npm/whatsapp-mcp

whatsapp-mcp@1.0.2

CAUTION

Publisher claims: "Production-grade Model Context Protocol (MCP) server for WhatsApp Web powered by Baileys" Observed in sandbox: sends data to 2a03:2880:f36e:120:face:b00c:0:167, 57.144.221.32.

Registry npm (MCP server)Publisher ahmadmcer · publishing for 9 daysInstalls 673Last detonated 1 h ago

Coverage

Server started and answered tools/list.
Tested
MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
Not tested
what the tools do when called with real credentials

Before you give it your token

It will ask for
WHATSAPP_AUTH_DIRConfiguration, not credentials: MCP_TRANSPORT, WHATSAPP_DATA_DIR, WHATSAPP_DB_FILE, WHATSAPP_LOGS_DIR, WHATSAPP_MEDIA_DIR, WHATSAPP_ROOT_DIR
Where it talks to
no vendor host named in the codeAlso whatsapp.com — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · contacted 2a03:2880:f36e:120:face:b00c:0:167, 57.144.221.32 (undeclared)
What we could not test
what the tools do when called with real credentials

Find out what these hosts are first. In the honeypot it contacted 2a03:2880:f36e:120:face:b00c:0:167, 57.144.221.32, which nothing in the package names as its own. If that is the vendor's service, fine; if you cannot place it, do not connect it.

$vet-skills run --net 2a03:2880:f36e:120:face:b00c:0:167,57.144.221.32 -- npx -y @ahmadmcer/whatsapp-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-16 and scored it 62/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths. Summary: sends data to 2a03:2880:f36e:120:face:b00c:0:167, 57.144.221.32.

Behavior trace

Honeypot run · 37 s · 2 scenarios
t+CategoryObserved action
0.0sprocessno install scripts in bundle
17sprocessdependency install exit 0
37snetworkdirect connection to 2a03:2880:f36e:120:face:b00c:0:167:0, bypassing the egress proxy · undeclared
37snetworkdirect connection to 57.144.221.32:0, bypassing the egress proxy · undeclared
37snetworkdirect connection to 57.144.221.32:443, bypassing the egress proxy · undeclared
37sclaimed19 tools: get_connection_status, request_pairing_code, logout, list_chats, get_chat_history, get_message_context, search_messages, mark_chat_read, send_message, send_media, react_to_message, download_media, list_contacts, get_contact_profile, list_groups, get_group_metadata, create_group, manage_group_participants, get_group_invite_link
37stoolse085816875a737bd
37stools0a33dbc817e16249
37stoolsfc2dbacaf65b757d
37stoolse24a077cd0d82490
37stools4ba91192e707cebc
37stoolsb71e70454bd22793
37stools3ec2f3d0d289edca
37stools1b5d09c77476ba13
37stoolse6acf328ce561df2
37stoolsf9750db559a6aeb1
37stools279f76e6b1fd8943
37stoolsd850ebc61fe7461b
37stools00ac6d4e26c15db2
37stools7c9cb616d7be152e
37stoolsf0fe2271696e2c8c
37stoolsa6c1638443350c00
37stools12b51d85c35c1e4b
37stoolsb6ce00e3cfbd9cdf
37stoolsf159b1b450230c1f
37sprocessscript backend runs setup only
37sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathsdist/login.js:32 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesdotenv.config({ path: path.join(WORKSPACE_ROOT, ".env") });Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/index.js:23 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesdotenv.config({ path: path.join(WORKSPACE_ROOT, ".env") });Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈61 tok
1 file · 7 in bundle
Tool list per prompt
≈2,349 tok
19 tools · 124 per tool
Handshake
1120 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 99

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for @ahmadmcer/whatsapp-mcp@1.0.2 as of 40 min ago. This is the package itself, not its dependencies.

What would make this Verified

18 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Contacts a host you did not declare≈ +23 on the totalList every host you talk to in SKILL.md frontmatter (`network: [api.example.com]`), or stop contacting the ones you cannot justify.
  2. Unclaimed publisher≈ +8 on the totalClaim ahmadmcer: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  3. Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
  4. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
Publish a new version to npm, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim ahmadmcerPropose a patch to the maintainer