WhatsApp MCP Server (Skael-GmbH/whatsapp-api-public) is an MCP server listed on the M8ven Trust Index. It scores 54 out of 100, grade D. It declares 16 tools. No publisher has claimed this listing.

D
Caution
54/100

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.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

Skael-GmbH

Source: Glama

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. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 11 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
16 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 2 credentials: JWT_SECRET, WHATSAPP_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes16 tools

These names and descriptions are the publisher's own, as the running server reported them. We print them as written. Our assessment is the findings above, not this list.

list_chats

List chats as the upstream API knows them.

list_contacts

List contacts known to the session.

list_groups

List groups the session participates in (derived from observed messages).

get_messages

Fetch message history for a single chat, most-recent first.

get_chat_overview

Composite read for "what's going on in my chats".

get_contact_presence

Get online/typing/last-seen presence for a contact.

get_contact_profile_picture

Get the profile picture URL (or data) for a contact.

get_message_status

Get delivery state and transition timestamps for a message id.

get_session_status

Check whether the WhatsApp session is connected and ready to send.

send_message

Send a text message to a contact or group.

edit_message

Edit a message you already sent (WhatsApp allows ~15 minutes).

delete_message

Delete a message you sent, for everyone in the chat.

send_media

Send an image/document/audio/video by uploading a local file.

send_location

Send a location card with lat/lng and optional name+address.

send_reaction

React to a specific message with an emoji.

mark_chat_read

Mark all unread messages in a chat as read.

// known CVEs in dependencies11 high9 medium4 low

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

highaxios@1.16.1GHSA-gcfj-64vw-6mp9

Axios Node HTTP adapter can use an inherited proxy after interceptor config cloning

highmulter@1.4.5-lts.2GHSA-44fp-w29j-9vj5

Multer vulnerable to Denial of Service via memory leaks from unclosed streams

highmulter@1.4.5-lts.2GHSA-4pg4-qvpc-4q3h

Multer vulnerable to Denial of Service from maliciously crafted requests

highmulter@1.4.5-lts.2GHSA-535w-7cp7-47q4

multer vulnerable to Denial of Service via oversized array index in field names

highmulter@1.4.5-lts.2GHSA-5528-5vmv-3xc2

Multer Vulnerable to Denial of Service via Uncontrolled Recursion

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configAPI_BASE_URLYour public URL, e.g. https://wa.example.com
configCORS_ORIGINYour public URL (not in production)
configFRONTEND_URLYour public URL, e.g. https://wa.example.com
configJWT_EXPIRES_IN
🔐 secretJWT_SECRETLong random string (dashboard login tokens)
configLOG_LEVEL
configMAX_FILE_SIZE
configRATE_LIMIT_MAX_REQUESTS
configRATE_LIMIT_WINDOW_MS
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_MAX_ATTEMPTS
configWEBHOOK_TIMEOUT
configWHATSAPP_API_BASE
🔐 secretWHATSAPP_API_KEY
configWHATSAPP_DEFAULT_SESSION
configMCP_HTTP_HOST
configMCP_HTTP_PORT
configMCP_HTTP_LOG_LEVEL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

0 critical, 11 high severity in production deps — axios@1.16.1 (high), multer@1.4.5-lts.2 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dependency freshness

1/22 production deps stale: swagger-ui-express@2024-05-31 (2.3y)

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// 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 Verified](https://m8ven.ai/badge/mcp/wazyee/whatsapp-api-public?variant=verified)](https://m8ven.ai/mcp/wazyee/whatsapp-api-public)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 84440b0cd3e1d519e0eceedd53422edc7913ae01
code hash: d30c8cdcc668d1552b3dd7aa796194115c25cc34c5c7d111002abdf8be11277c
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client