WhatsApp MCP Stream (BusinessNone/WhatsAppMCP) is an MCP server listed on the M8ven Trust Index. It scores 47 out of 100, grade D. It declares 29 tools. No publisher has claimed this listing.

D
Caution
47/100

WhatsApp MCP Stream

Enables programmatic WhatsApp automation through MCP, including sending messages, managing chats and contacts, searching conversation history, and exchanging media files.

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

BusinessNone

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: 2 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
⚠️
Tests do not pass
Either the test suite is broken or the code regressed. Either way the published behaviour can’t be verified by the publisher’s own tests.
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: REQUIRE_UPLOAD_TOKEN, UPLOAD_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 high9 medium1 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@2.1.1GHSA-72gw-mp4g-v24j

Multer vulnerable to Denial of Service via deeply nested field names

mediumaxios@1.16.1GHSA-42h9-826w-cgv3

Axios: Excessive recursion in formDataToJSON can cause denial of service

mediumaxios@1.16.1GHSA-7q8q-rj6j-mhjq

Axios: Nested axios option objects can consume polluted prototype values

mediumaxios@1.16.1GHSA-f4gw-2p7v-4548

Axios: NO_PROXY bypass for 0.0.0.0 local addresses in axios

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.
configAUTO_DOWNLOAD_MAX_MB
configAUTO_DOWNLOAD_MEDIA
configAUTO_SELECT_CONTACT
configBAILEYS_LOG_LEVEL
configDB_PATHSQLite database path for chats/messages persistence.
configFFMPEG_PATH
configLOG_LEVEL
configMCP_HTTP_ENABLE_JSON_RESPONSEUse direct JSON responses for Streamable HTTP POST requests by default. Set to 0 to force the older SSE-style POST response handling.
configMEDIA_DIRSettings can be edited in the admin UI and are persisted to SETTINGS_PATH (defaults to /settings.json).
configMEDIA_PUBLIC_BASE_URL
configPUBLIC_BASE_URL
🔐 secretREQUIRE_UPLOAD_TOKEN
configSESSION_DIRSQLite database path for chats/messages persistence.
configSETTINGS_PATHSettings can be edited in the admin UI and are persisted to (defaults to MEDIA_DIR/settings.json).
configTRANSPORT
configUPLOAD_ENABLED
configUPLOAD_MAX_FILES
configUPLOAD_MAX_MB
🔐 secretUPLOAD_TOKEN
configWA_AUTO_DOWNLOAD_CONCURRENCYMax parallel auto-downloads. Auto-download runs through an in-process bounded queue so a burst of inbound media cannot saturate the I/O.
configWA_AUTO_DOWNLOAD_QUEUE_MAXMax queued auto-download jobs. Excess is dropped FIFO (oldest first) with a warning log; recent messages stay prioritised.
configWA_DISCONNECT_RECOVERY_DELAY_MSHow long to wait after a socket close before the disconnect watchdog forces reconnect/restart.
configWA_DISCONNECT_RECOVERY_RESTART_CODESComma-separated disconnect status codes that should escalate straight to an internal restart watchdog.
configWA_EVENT_LOGEnable detailed WhatsApp event logs.
configWA_EVENT_STREAMWrite raw Baileys event stream to a file for deep debugging.
configWA_EVENT_STREAM_PATHFile path for the event stream log.
configWA_IDEMPOTENCY_TTL_MSHow long completed send_message idempotency records are retained in SQLite for safe retries.
configWA_INITIALIZE_TIMEOUT_MSRace the WhatsApp client initialise against this deadline; set to 0 to disable. Throws on timeout so recovery can retry instead of hanging.
configWA_MESSAGE_INDEX_MAXMax in-memory entries for message index (jid:id -> raw message).
configWA_MESSAGE_KEY_INDEX_MAXMax in-memory entries for message key index (id -> raw message).
configWA_READINESS_GRACE_MSGrace period during recovery/disconnect before /healthz turns unhealthy.
configWA_RESYNC_RECONNECTEnable reconnect safety net after force resync.
configWA_RESYNC_RECONNECT_DELAY_MSDelay before reconnect after force resync (ms).
configWA_SEND_DEDUP_WINDOW_MSSuppress exact duplicate send_message requests to the same JID within this window.
configWA_SYNC_RECOVERY_COOLDOWN_MSMinimum delay between automatic app-state recoveries.
configWA_SYNC_RECOVERY_WINDOW_MSTime window used to count repeated app-state corruption failures.
configWA_SYNC_SOFT_RECOVERY_LIMITNumber of soft recoveries before escalating to an internal restart.
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

29/29 tools missing one or more hints — ping (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_qr_code (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); check_auth_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +26 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — send_media deletes at line 183 (fs.unlinkSync(tempFilePath))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Tool inputs are validated

Only 9/29 tool handlers declare input schemas (31%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool test coverage

Only 3/29 tools referenced in tests (10%)

Write tests that reference each tool by name so every tool has at least one test.

Tests pass

npm test failed — tests do not pass

Make sure npm test runs cleanly. Common cause: missing build step or missing env vars.

Production dependencies are patched

0 critical, 2 high severity in production deps — axios@1.16.1 (high), multer@2.1.1 (high)

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

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 7 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/businessnone/whatsappmcp?variant=verified)](https://m8ven.ai/mcp/businessnone/whatsappmcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: b10630d05ab63be85a10c842731fec412ffe36bb
code hash: cff961e102f48ab99fe9e00fecaae4404dc3cc6a1bf4109c753fb936d7682789
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