uni-msg WhatsApp
NPM · UNI-MSG-MCP-SERVER · 2 COMPONENTS · SCANNED SEP 20
Drive WhatsApp from any MCP client: pair devices, send text and media, manage contacts and groups.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 26 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1043 tokens (~80/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 71% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 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 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the uni-msg WhatsApp MCP server?
uni-msg WhatsApp runs locally as an npm package, launched with npx -y uni-msg-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · uni-msg-mcp-server
claude mcp add com-uni-msg-whatsapp -- npx -y uni-msg-mcp-server
{
"mcpServers": {
"com-uni-msg-whatsapp": {
"command": "npx",
"args": [
"-y",
"uni-msg-mcp-server"
]
}
}
} {
"servers": {
"com-uni-msg-whatsapp": {
"command": "npx",
"args": [
"-y",
"uni-msg-mcp-server"
]
}
}
} codex mcp add com-uni-msg-whatsapp -- npx -y uni-msg-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-uni-msg-whatsapp": {
"type": "local",
"command": [
"npx",
"-y",
"uni-msg-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add com-uni-msg-whatsapp --command npx --arg -y --arg uni-msg-mcp-server
mcp_servers:
com-uni-msg-whatsapp:
command: "npx"
args: ["-y", "uni-msg-mcp-server"] {
"McpServers": {
"com-uni-msg-whatsapp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"uni-msg-mcp-server"
]
}
}
} assistant mcp add com-uni-msg-whatsapp -t stdio -c npx -a -y uni-msg-mcp-server
{
"mcpServers": {
"com-uni-msg-whatsapp": {
"command": "npx",
"args": [
"-y",
"uni-msg-mcp-server"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed npm/uni-msg-mcp-server@0.3.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
connect_device ~131
Step 2 of 3. Starts a session and returns an 8-character pairing code (and sometimes a QR string). Give the user the code and these exact instructions: on the phone holding that number, open WhatsApp → Settings → Linked devices → Link a device → "Link with phone number instead", then type the code. The code expires in about two minutes; if it lapses, call request_pairing_code for a fresh one rather than connect_device again. After they enter it, poll get_device_status until it reports connected.
| Name | Type | Req | Description |
|---|---|---|---|
| deviceId | string | yes | From create_device or list_devices. |
No output schema declared.
No examples provided.
create_device ~123
Register a new WhatsApp number so it can be paired. Step 1 of 3: create_device, then connect_device to get a pairing code, then the user enters that code on their phone. Creating a device may consume a slot on the account's plan, so check list_devices first rather than creating a duplicate for a number that already exists.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | A label for this device, e.g. "Sales line". |
| phoneNumber | string | yes | The number to pair, in international format, e.g. +971501234567. |
No output schema declared.
No examples provided.
disconnect_device ~49
End a device session. The number stays registered and can be reconnected later, but it stops sending and receiving immediately, so confirm with the user before calling this.
| Name | Type | Req | Description |
|---|---|---|---|
| deviceId | string | yes | – |
No output schema declared.
No examples provided.
get_device_status ~59
Check one device: whether it is connected, and when it was last seen. Use when a send fails, to tell a disconnected device from a bad recipient.
| Name | Type | Req | Description |
|---|---|---|---|
| deviceId | string | yes | Device id, e.g. dev_abc123 |
No output schema declared.
No examples provided.
list_contacts ~45
List saved contacts, optionally filtered by a search term.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Default 25, max 100. |
| search | string | – | Match against name or number. |
No output schema declared.
No examples provided.
list_conversations ~82
List recent WhatsApp conversations for a device — who has been in touch and when. Use this to find the "peer" value that read_thread needs.
| Name | Type | Req | Description |
|---|---|---|---|
| deviceId | string | – | Optional. Omit to span all devices. |
| limit | number | – | Default 50, max 500. |
| search | string | – | Match against name or number. |
No output schema declared.
No examples provided.
list_devices ~47
List the WhatsApp devices on this account with their connection status. Use this first — every send needs a deviceId, and only a device whose status is "connected" can deliver a message.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_groups ~49
List WhatsApp groups a device belongs to, with their JIDs. Use the JID as the "to" value in send_message to post to a group.
| Name | Type | Req | Description |
|---|---|---|---|
| deviceId | string | yes | – |
No output schema declared.
No examples provided.
read_thread ~98
Read the message history with one contact or group. "peer" is the other party's phone number or JID, as returned by list_conversations. Returns newest first; use page to go further back.
| Name | Type | Req | Description |
|---|---|---|---|
| deviceId | string | yes | – |
| limit | number | – | Default 30, max 100. |
| page | number | – | Default 1. |
| peer | string | yes | Phone number or JID of the other party. |
No output schema declared.
No examples provided.
request_pairing_code ~54
Issue a fresh pairing code for a device that is already connecting. Use this when the previous code expired — it is cheaper and more reliable than tearing the session down and starting again.
| Name | Type | Req | Description |
|---|---|---|---|
| deviceId | string | yes | – |
No output schema declared.
No examples provided.
send_media ~117
Send an image, video, audio clip or document by public URL. The URL must be reachable by uni-msg — a local file path will not work. Sends immediately; confirm the recipient first.
| Name | Type | Req | Description |
|---|---|---|---|
| caption | string | – | Optional. Ignored for audio. |
| deviceId | string | yes | – |
| fileName | string | – | Optional, for documents. |
| kind | string | yes | – |
| mediaUrl | string | yes | Publicly reachable https URL. |
| to | string | yes | Phone number in international format, or a JID. |
No output schema declared.
No examples provided.
send_message ~126
Send a WhatsApp text message. The recipient may be a phone number in international format without "+" (e.g. 971501234567), or a JID for a group (…@g.us) or LID (…@lid). Sends immediately — there is no undo, so confirm the recipient with the user before calling this.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Message text, up to 4096 characters. |
| deviceId | string | yes | Which device sends it. See list_devices. |
| to | string | yes | Phone number in international format, or a JID. |
No output schema declared.
No examples provided.
upsert_contact ~63
Create a contact, or update it if the number already exists. Matching is by phone number, so this will not create a duplicate.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | – | |
| name | string | – | – |
| phoneNumber | string | yes | International format, no "+". |
No output schema declared.
No examples provided.
What is the uni-msg WhatsApp MCP server?
uni-msg WhatsApp is an MCP server listed in the public MCP registry as com.uni-msg/whatsapp. Drive WhatsApp from any MCP client: pair devices, send text and media, manage contacts and groups. This page covers its npm package (uni-msg-mcp-server).
Is the uni-msg WhatsApp MCP server safe to use?
uni-msg WhatsApp scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 uni-msg WhatsApp MCP server expose?
uni-msg WhatsApp exposes 13 tools: list_devices, get_device_status, create_device, connect_device, request_pairing_code, and 8 more. Their descriptions and schemas cost roughly 1,043 tokens of context every time the server is loaded.
Is the uni-msg WhatsApp MCP server still maintained?
uni-msg WhatsApp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the uni-msg WhatsApp MCP server under?
uni-msg WhatsApp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.