Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

WhatsApp MCP

PYPI · ADELAIDASOFIA-WHATSAPP-MCP · SCANNED SEP 13

WhatsApp MCP. SQLCipher-encrypted, scrubber-CI-gated, draft-and-confirm sends, voice transcription.

0 this week 79 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 2 of 26 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 848 tokens (~77/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 91% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_message" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the WhatsApp MCP server?

WhatsApp MCP runs locally as a PyPI package, launched with uvx adelaidasofia-whatsapp-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · adelaidasofia-whatsapp-mcp

# add to Claude Code
claude mcp add adelaidasofia-whatsapp-mcp -- uvx adelaidasofia-whatsapp-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "adelaidasofia-whatsapp-mcp": {
      "command": "uvx",
      "args": [
        "adelaidasofia-whatsapp-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "adelaidasofia-whatsapp-mcp": {
      "command": "uvx",
      "args": [
        "adelaidasofia-whatsapp-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add adelaidasofia-whatsapp-mcp -- uvx adelaidasofia-whatsapp-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "adelaidasofia-whatsapp-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "adelaidasofia-whatsapp-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add adelaidasofia-whatsapp-mcp --command uvx --arg adelaidasofia-whatsapp-mcp
# ~/.hermes/config.yaml
mcp_servers:
  adelaidasofia-whatsapp-mcp:
    command: "uvx"
    args: ["adelaidasofia-whatsapp-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "adelaidasofia-whatsapp-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "adelaidasofia-whatsapp-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add adelaidasofia-whatsapp-mcp -t stdio -c uvx -a adelaidasofia-whatsapp-mcp
// mcp.json
{
  "mcpServers": {
    "adelaidasofia-whatsapp-mcp": {
      "command": "uvx",
      "args": [
        "adelaidasofia-whatsapp-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 12 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 11 Sept 26 +1
    • Stability: 0.97 → pass security
  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 5 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 4 Sept 26 +1
    • Stability: 0.97 → pass security
  • 3 Sept 26 0
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
  • 2 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 13 Sept 2026 · Analysed pypi/adelaidasofia-whatsapp-mcp@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 26 packages
Packages resolved 26
Stale 1
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~848 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
confirm_send ~45

Commit a previously-drafted send. This is where the actual WhatsApp network send happens.

NameTypeReqDescription
draft_idstringyesThe draft_id returned by a previous send_message call.

Structured output declared, but exposes no named fields.

No examples provided.

healthcheck ~27

Check the Go bridge is running and authenticated. Returns status, schema version, and feature flags.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_chats ~68

List WhatsApp chats with metadata. Sorted by most recent message time.

NameTypeReqDescription
limitintegerMax chats to return (default 20, max 200).
offsetintegerPagination offset.
unread_onlybooleanIf true, return only chats with unread messages.

Structured output declared, but exposes no named fields.

No examples provided.

list_messages ~115

List messages in a chat. Most recent first by default.

NameTypeReqDescription
beforeReturn messages older than this message ID (pagination).
chat_jidstringyesThe JID of the chat (from list_chats or search_contacts).
include_crm_contextbooleanWhen true and WHATSAPP_VAULT_CRM_PATH is set, the response includes a `crm_context` block with the matching vault CRM note summary.
limitintegerMax messages (default 20, max 500).

Structured output declared, but exposes no named fields.

No examples provided.

mark_chat_read ~95

Mark one or more messages as read. Affects your WhatsApp unread count on this device AND across your linked devices. Low-consequence: no draft+confirm needed, this is a one-step call.

NameTypeReqDescription
chat_jidstringyesThe chat to mark read.
message_idsarrayyesList of message IDs to mark. Typically the IDs of the most recent unread messages for this chat.

Structured output declared, but exposes no named fields.

No examples provided.

search_contacts ~62

Find contacts by name or phone number. Accent-insensitive. "Muñoz" matches "munoz", "José" matches "jose", "Zürich" matches "zurich".

NameTypeReqDescription
limitinteger
querystringyes

Structured output declared, but exposes no named fields.

No examples provided.

send_message ~129

Create a DRAFT text message. Does NOT send until confirm_send is called. Returns a draft_id plus the resolved recipient display name, a preview, and an expires_at timestamp. Drafts expire after 1 hour. Each draft can be confirmed at most once.

NameTypeReqDescription
recipient_jidstringyesThe recipient's WhatsApp JID (e.g. from list_chats or search_contacts). Must include the @s.whatsapp.net or @g.us suffix.
textstringyesThe message text. No media / reactions / voice in v0.3.0.

Structured output declared, but exposes no named fields.

No examples provided.

send_reaction ~90

Create a DRAFT emoji reaction on a specific message.

NameTypeReqDescription
emojistringyesThe reaction emoji (e.g., "❤️", "👍", "😂"). Pass "" to remove a previous reaction.
recipient_jidstringyesThe chat JID where the target message lives.
target_message_idstringyesThe ID of the message to react to. Find via list_messages.

Structured output declared, but exposes no named fields.

No examples provided.

send_reply_quote ~99

Create a DRAFT reply-quote message that cites a specific earlier message. The recipient will see the original quoted message appear above your reply in their WhatsApp UI (the familiar reply-indicator format).

NameTypeReqDescription
quoted_message_idstringyesThe ID of the message being quoted. Find it via list_messages.
recipient_jidstringyesThe chat JID (direct or group).
textstringyesThe reply text.

Structured output declared, but exposes no named fields.

No examples provided.

send_typing_indicator ~64

Show a "typing..." or "paused" indicator to the chat recipient.

NameTypeReqDescription
chat_jidstringyesThe chat to signal.
statestring"composing" (typing) or "paused" (stopped typing). Default: composing.

Structured output declared, but exposes no named fields.

No examples provided.

set_online_presence ~54

Signal your online/offline presence globally to all chats. Changing this affects your "last seen" visibility per WhatsApp's privacy settings.

NameTypeReqDescription
onlinebooleanTrue to appear online, False to appear offline.

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the WhatsApp MCP server?

WhatsApp MCP is listed in the public MCP registry as io.github.adelaidasofia/whatsapp-mcp. WhatsApp MCP. SQLCipher-encrypted, scrubber-CI-gated, draft-and-confirm sends, voice transcription. This page covers its PyPI package (adelaidasofia-whatsapp-mcp).

Is the WhatsApp MCP server safe to use?

WhatsApp MCP scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 13 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the WhatsApp MCP server expose?

WhatsApp MCP exposes 11 tools: healthcheck, list_chats, search_contacts, list_messages, send_message, and 6 more. Their descriptions and schemas cost roughly 848 tokens of context every time the server is loaded.

Is the WhatsApp MCP server still maintained?

WhatsApp MCP is still listed as active in the MCP registry. We last reached this channel on 13 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.