# uni-msg WhatsApp (npm · uni-msg-mcp-server)

Drive WhatsApp from any MCP client: pair devices, send text and media, manage contacts and groups.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `uni-msg.com`: 33/100, [markdown](https://verifymcp.io/servers/com-uni-msg-whatsapp/uni-msg.md), [page](https://verifymcp.io/servers/com-uni-msg-whatsapp/uni-msg)
- npm · `uni-msg-mcp-server`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-uni-msg-whatsapp/uni-msg-mcp-server.md), [page](https://verifymcp.io/servers/com-uni-msg-whatsapp/uni-msg-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `uni-msg-mcp-server`
- Version: `0.3.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 26 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1043 tokens (~80/item across 13 items; 13 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 71% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add com-uni-msg-whatsapp -- npx -y uni-msg-mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "com-uni-msg-whatsapp": {
      "command": "npx",
      "args": [
        "-y",
        "uni-msg-mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-uni-msg-whatsapp": {
      "command": "npx",
      "args": [
        "-y",
        "uni-msg-mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-uni-msg-whatsapp -- npx -y uni-msg-mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-uni-msg-whatsapp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "uni-msg-mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-uni-msg-whatsapp --command npx --arg -y --arg uni-msg-mcp-server
```

### Hermes

```yaml
mcp_servers:
  com-uni-msg-whatsapp:
    command: "npx"
    args: ["-y", "uni-msg-mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-uni-msg-whatsapp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "uni-msg-mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-uni-msg-whatsapp -t stdio -c npx -a -y uni-msg-mcp-server
```

### Other

```json
{
  "mcpServers": {
    "com-uni-msg-whatsapp": {
      "command": "npx",
      "args": [
        "-y",
        "uni-msg-mcp-server"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 75, +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.

### 2026-09-17 (score 74, +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.

### 2026-09-14 (score 73, +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.

### 2026-09-12 (score 72, +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.

### 2026-09-10 (score 71, +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.

### 2026-09-08 (score 70, +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.

### 2026-09-06 (score 69, +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.

### 2026-09-04 (score 68, +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.

## MCP tools (13)

### `list_devices` (~47 tokens)

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.

### `get_device_status` (~59 tokens)

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.

Input parameters:

- `deviceId` (string, required): Device id, e.g. dev_abc123

### `create_device` (~123 tokens)

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.

Input parameters:

- `name` (string, required): A label for this device, e.g. "Sales line".
- `phoneNumber` (string, required): The number to pair, in international format, e.g. +971501234567.

### `connect_device` (~131 tokens)

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.

Input parameters:

- `deviceId` (string, required): From create_device or list_devices.

### `request_pairing_code` (~54 tokens)

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.

Input parameters:

- `deviceId` (string, required)

### `disconnect_device` (~49 tokens)

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.

Input parameters:

- `deviceId` (string, required)

### `send_message` (~126 tokens)

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.

Input parameters:

- `content` (string, required): Message text, up to 4096 characters.
- `deviceId` (string, required): Which device sends it. See list_devices.
- `to` (string, required): Phone number in international format, or a JID.

### `send_media` (~117 tokens)

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.

Input parameters:

- `caption` (string): Optional. Ignored for audio.
- `deviceId` (string, required)
- `fileName` (string): Optional, for documents.
- `kind` (string, required)
- `mediaUrl` (string, required): Publicly reachable https URL.
- `to` (string, required): Phone number in international format, or a JID.

### `list_contacts` (~45 tokens)

List saved contacts, optionally filtered by a search term.

Input parameters:

- `limit` (number): Default 25, max 100.
- `search` (string): Match against name or number.

### `upsert_contact` (~63 tokens)

Create a contact, or update it if the number already exists. Matching is by phone number, so this will not create a duplicate.

Input parameters:

- `email` (string)
- `name` (string)
- `phoneNumber` (string, required): International format, no "+".

### `list_conversations` (~82 tokens)

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.

Input parameters:

- `deviceId` (string): Optional. Omit to span all devices.
- `limit` (number): Default 50, max 500.
- `search` (string): Match against name or number.

### `read_thread` (~98 tokens)

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.

Input parameters:

- `deviceId` (string, required)
- `limit` (number): Default 30, max 100.
- `page` (number): Default 1.
- `peer` (string, required): Phone number or JID of the other party.

### `list_groups` (~49 tokens)

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.

Input parameters:

- `deviceId` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-uni-msg-whatsapp/uni-msg-mcp-server#diagnostics

## Score history

- 2026-09-20: 75
- 2026-09-19: 75
- 2026-09-18: 74
- 2026-09-17: 74
- 2026-09-16: 73
- 2026-09-15: 73
- 2026-09-14: 73
- 2026-09-13: 72
- 2026-09-12: 72
- 2026-09-11: 71
- 2026-09-10: 71
- 2026-09-09: 70
- 2026-09-08: 70
- 2026-09-07: 69
- 2026-09-06: 69
- 2026-09-05: 68
- 2026-09-04: 68
- 2026-09-03: 67
- 2026-09-02: 67
- 2026-09-01: 66
- 2026-08-31: 63
- 2026-08-30: 63
- 2026-08-29: 63
- 2026-08-28: 63
- 2026-08-27: 63
- 2026-08-26: 63
- 2026-08-25: 63

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/uni-msg-mcp-server
- Socket report: https://socket.dev/npm/package/uni-msg-mcp-server
- Website: https://uni-msg.com/blog/whatsapp-mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-uni-msg-whatsapp/uni-msg-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-uni-msg-whatsapp/uni-msg-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/com-uni-msg-whatsapp/uni-msg-mcp-server