Whatsapp Web (mario-andreschak) MCP Server

mcp-whatsapp-web npm v1.2.0

Published by mario-andreschak — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

TypeScript MCP server for WhatsApp using whatsapp-web.js

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 3

high Shell/command execution in server code (dist/utils/browser-process-manager.js)MTC-SRC-002

In the server's implementation (`dist/utils/browser-process-manager.js:4`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: exec, execFile } from 'child_process'; import { promisify } from 'util'; const execAsync = promisify(exec); const execF

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/utils/browser-process-manager.js

high Shell/command execution in server code (dist/utils/cleanup-browsers.js)MTC-SRC-002

In the server's implementation (`dist/utils/cleanup-browsers.js:12`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: / import { exec } from 'child_process'; import { promisify } from 'util'; import { log } from './logger.js'; import { Br

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/utils/cleanup-browsers.js

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([download_media, get_message_context]) co-exist with external-action tools ([send_message]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [download_media, get_message_context] → sinks [send_message]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow download_media → send_message

Tools 18

Each tool and what it can reach — statically extracted from the published source.

  • download_mediaingests untrusted input
  • get_message_contextingests untrusted input
  • send_messagenetwork egress
  • check_auth_statusno sensitive capability
  • get_backend_statusno sensitive capability
  • get_chat_by_idno sensitive capability
  • get_contact_by_idno sensitive capability
  • get_direct_chat_by_contact_numberno sensitive capability
  • get_last_interactionno sensitive capability
  • get_message_by_idno sensitive capability
Show 8 more tools ↓
  • get_qr_codeno sensitive capability
  • list_chatsno sensitive capability
  • list_messagesno sensitive capability
  • logoutno sensitive capability
  • pingno sensitive capability
  • request_pairing_codeno sensitive capability
  • search_contactsno sensitive capability
  • send_mediano sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 2

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.2.0 latest A 93/100 3 1.13.0 2026-09-07
v1.1.0 A 93/100 3 1.13.0 2026-09-05

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-whatsapp-web/badge.svg)](https://mcptrustchecker.com/registry/mcp-whatsapp-web)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-whatsapp-web"><img src="https://mcptrustchecker.com/registry/mcp-whatsapp-web/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-whatsapp-web/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mcp-whatsapp-web --online

Use the free API → How scoring works

Other implementations of Whatsapp Web 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Productivity & Workflow