54
/ 100
22 days ago
glama

WhatsApp MCP Server

Enables Claude to read and send WhatsApp messages through a self-hosted REST API, supporting multi-user sessions, media, groups, contacts, and webhooks.

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find.

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
⚠️
Known vulnerabilities in dependencies: 16 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
14 tools verified — handlers match their declared behaviour
9 read-only tools verified — handlers contain no write/delete/exec
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 3 credentials: JWT_SECRET, REGISTER_PASSWORD, WHATSAPP_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies16 high14 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

highaxios@1.6.0GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

highaxios@1.6.0GHSA-3g43-6gmg-66jw

axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

highaxios@1.6.0GHSA-43fc-jf86-j433

Axios is Vulnerable to Denial of Service via __proto__ Key in mergeConfig

highaxios@1.6.0GHSA-4hjh-wcwx-xvwj

Axios is vulnerable to DoS attack through lack of data size check

highaxios@1.6.0GHSA-6chq-wfr3-2hj9

Axios: Header Injection via Prototype Pollution

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// required environment variables
This server reads these from process.env. You'll be asked to provide them before it can run.
configAPI_BASE_URL/ FRONTEND_URL Your public URL, e.g. https://wa.example.com
configCORS_ORIGINYour public URL (not in production)
configFRONTEND_URLAPI_BASE_URL / Your public URL, e.g. https://wa.example.com
configJWT_EXPIRES_IN
🔐 secretJWT_SECRETedit .env — set DATABASE_URL, , REGISTER_PASSWORD (see below)
configLOG_LEVEL
configMAX_FILE_SIZE
configPORT
configRATE_LIMIT_MAX_REQUESTS
configRATE_LIMIT_WINDOW_MS
🔐 secretREGISTER_PASSWORDedit .env — set DATABASE_URL, JWT_SECRET, (see below)
configWA_PROXY_COUNTRYOptional: WA_PROXY_URL / to route WhatsApp connections through a residential proxy (helps if your server IP is flagged).
configWA_PROXY_URLOptional: / WA_PROXY_COUNTRY to route WhatsApp connections through a residential proxy (helps if your server IP is flagged).
configWEBHOOK_TIMEOUT
configWHATSAPP_API_BASEe =https://your-domain.com \
🔐 secretWHATSAPP_API_KEYe =<your apiKey> \
configWHATSAPP_DEFAULT_SESSIONe =my-session \
// full audit trail
The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.
// improvement guidance — verified publishers only
We have 2 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/wazyee-whatsapp-api-public-s0ox07)](https://m8ven.ai/mcp/wazyee-whatsapp-api-public-s0ox07)
commit: 9944d37e8e59da390ebb7f77da43b76f22ae4993
code hash: 3160172d2b5d09672aed3b37e162b5bc705e9e1896ca735c139e512dfd84b0db
verified: 7/9/2026, 10:01:48 AM
view raw JSON →