Wappmcp MCP Server
wappmcp
npm
v0.4.0
Source verified
Published by vaibhavpandeyvpz — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
TypeScript stdio MCP server and CLI for WhatsApp Web.
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 − 1.2 = 99. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −1.2 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
2. Client adoption risk — 99 − 3 = 96. 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:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
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 2
medium Untrusted input can drive an external actionMTC-FLOW-005
Untrusted-input tools ([whatsapp_get_chat_messages]) co-exist with external-action tools ([whatsapp_send_message, whatsapp_forward_message]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [whatsapp_get_chat_messages] → sinks [whatsapp_send_message, whatsapp_forward_message]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow whatsapp_get_chat_messages → whatsapp_send_message
low Package runs install-time scripts (postinstall)MTC-SUP-010
"wappmcp" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.
Evidence: patch-package
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package wappmcp
Tools 22
Each tool and what it can reach — statically extracted from the published source.
whatsapp_forward_messagenetwork egresswhatsapp_get_chat_messagesingests untrusted inputwhatsapp_send_messagenetwork egresswhatsapp_delete_messageno sensitive capabilitywhatsapp_edit_messageno sensitive capabilitywhatsapp_get_chatno sensitive capabilitywhatsapp_get_chat_participantsno sensitive capabilitywhatsapp_get_contactno sensitive capabilitywhatsapp_get_contact_lidno sensitive capabilitywhatsapp_get_meno sensitive capability
Show 12 more tools ↓
whatsapp_get_messageno sensitive capabilitywhatsapp_get_statusno sensitive capabilitywhatsapp_list_chatsno sensitive capabilitywhatsapp_list_contactsno sensitive capabilitywhatsapp_lookup_numberno sensitive capabilitywhatsapp_react_to_messageno sensitive capabilitywhatsapp_reply_to_messageno sensitive capabilitywhatsapp_search_contactsno sensitive capabilitywhatsapp_search_messagesno sensitive capabilitywhatsapp_send_media_from_base64no sensitive capabilitywhatsapp_send_media_from_pathno sensitive capabilitywhatsapp_send_typingno 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
- Tools were statically extracted from the published source (22 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.4.0 latest |
A 96/100 | 2 | 1.13.0 | 2026-09-09 |
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.
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 wappmcp --onlineMore in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Generates production-ready UI components from natural language, inspired by v0.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.