# WhaTools — WhatsApp tools (remote · wha.tools)

WhatsApp tools: wa.me links, QR codes, share widgets, phone validation, API rate card & limits.

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-08

## Components

- remote · `wha.tools`: 61/100 (this document), [markdown](https://verifymcp.io/servers/tools-wha-whatsapp-tools/api-mcp.md), [page](https://verifymcp.io/servers/tools-wha-whatsapp-tools/api-mcp)

## Channel facts

- Endpoint: `https://wha.tools/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.74.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-08-08.

- **Endpoint Security**: 60/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1641 tokens (~205/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add --transport http tools-wha-whatsapp-tools https://wha.tools/api/mcp
```

### Codex

```toml
[mcp_servers.tools-wha-whatsapp-tools]
url = "https://wha.tools/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tools-wha-whatsapp-tools": {
      "type": "remote",
      "url": "https://wha.tools/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tools-wha-whatsapp-tools --url https://wha.tools/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tools-wha-whatsapp-tools:
    url: "https://wha.tools/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "tools-wha-whatsapp-tools": {
      "type": "http",
      "url": "https://wha.tools/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-08-08 (score 61)

First indexed and scored.

## MCP tools (8)

### `generate_whatsapp_link` (~87 tokens)

Generate a WhatsApp click-to-chat (wa.me) link with an optional phone number and pre-filled message. Runs locally; no message is sent.

Input parameters:

- `message` (string): The message to pre-fill in the chat (optional).
- `phone` (string): Recipient phone number in international format (digits only; optional). Omit to create a share link with no specific recipient.

### `generate_bulk_whatsapp_links` (~274 tokens)

Generate personalized WhatsApp click-to-chat (wa.me) links for a list of contacts from one message template. Everything uses a single {{…}} syntax: {{field}} placeholders are replaced per contact; {{field|fallback}} supplies a default for empty/missing fields; {{FirstName}} is derived from a name field; and {{option a|option b}} spintax (a group whose first option is not a field) picks one variation per contact (stable per number) so messages are not identical. Returns a JSON array of {phone, message, link}. Runs locally; no message is sent — each link opens WhatsApp with the text pre-filled and a human taps send.

Input parameters:

- `contacts` (array, required): Up to 500 contacts. Each needs a "phone" (international format, digits only) plus any placeholder fields as string properties.
- `template` (string, required): Message template with {{field}} placeholders, e.g. 'Hello {{name}}, see you at {{time}}'. Supports {{field|fallback}} defaults, {{FirstName}} derived from a name field, and {{a|b|c}} spintax variatio…

### `validate_phone_number` (~168 tokens)

Validate and inspect a phone number with libphonenumber: whether it is valid (a real, allocated number) and/or possible (right length), its country, calling code, line type (mobile / landline / VoIP / toll-free / …) and every standard format (E.164, international, national) plus a wa.me link. Runs locally and offline. Does NOT check whether the number is registered on WhatsApp — there is no such API here.

Input parameters:

- `country` (string): ISO 3166-1 alpha-2 country code (e.g. "GB", "US") assumed when the number has no country code. Optional.
- `phone` (string, required): The phone number to validate. International format with a leading "+" is best; otherwise also pass `country`.

### `generate_whatsapp_qr` (~76 tokens)

Generate a scannable QR code (as an SVG) for a WhatsApp click-to-chat link with an optional phone number and pre-filled message.

Input parameters:

- `message` (string): The message to pre-fill in the chat (optional).
- `phone` (string): Recipient phone number in international format (digits only; optional).

### `build_whatsapp_share_widget` (~191 tokens)

Build embeddable "Share on WhatsApp" widget HTML (web and email variants) with a link preview card and a pre-filled message. Returns self-contained HTML.

Input parameters:

- `buttonPlacement` (string): Where to place the share button relative to the card (optional).
- `buttonText` (string): Call-to-action button text (optional; defaults to "Share on WhatsApp").
- `description` (string, required): Message text shown above the card (supports *bold*, _italic_, ~strike~).
- `domain` (string): Domain label shown on the card (optional).
- `includeCredit` (boolean): Append a small "Widget by wha.tools" credit line under the widget (optional; default false).
- `thumbnail` (string): Preview image URL (optional).
- `title` (string, required): Title shown on the preview card.
- `url` (string, required): The URL being shared.

### `estimate_whatsapp_api_cost` (~280 tokens)

Estimate the monthly WhatsApp Business (Cloud) API cost under Meta's current per-message pricing (in effect since 1 July 2025). Given a country/market and monthly volumes of marketing, utility and authentication template messages, returns an itemized breakdown and total in USD. Marketing is always billed; utility can be reduced by the share sent inside a free 24-hour service window; authentication is billed at the lowest rates; service replies are free. Runs locally. This is Meta's platform fee only — a BSP/provider adds its own fee on top, so treat it as a floor, not a quote.

Input parameters:

- `authentication` (number): Monthly count of authentication template messages (one-time passcodes).
- `market` (string, required): Recipient market as a 2-letter code (e.g. "US", "IN", "BR", "GB", "DE"), or "ROW" for rest of world. Rates vary widely by market.
- `marketing` (number): Monthly count of marketing template messages (promotions, offers).
- `utility` (number): Monthly count of utility template messages (order updates, receipts, reminders).
- `utility_free_within_window_pct` (number): Percentage (0–100) of utility messages sent inside a free 24-hour customer-service window; these are not billed. Optional, default 0.

### `get_whatsapp_rates` (~335 tokens)

Look up Meta's official WhatsApp Business (Cloud) API per-message rates from the site's dated rate card — the same figures the pricing calculator uses, so prefer this over recalling or guessing prices. Give a market to get one row, or omit it for every market in the chosen currency. Returns the current list price per template category (marketing, utility, authentication, and authentication-international where a market has one), the currency, the effective and last-verified dates, the source link and the CC BY licence. Optionally include the published volume-tier thresholds and rates for a single market. This is Meta's platform fee only — a BSP/provider adds its own fee on top, so treat it as a floor. Runs locally.

Input parameters:

- `currency` (string): One of the 16 currencies Meta publishes a card in (USD, EUR, GBP, INR, IDR, BRL, MXN, ARS, COP, AED, SAR, AUD, MYR, PEN, CLP, SGD). Rates are stored per currency exactly as Meta prints them, never co…
- `include_tiers` (boolean): When a single market is given, also return that market's published volume-tier thresholds and per-band rates for utility and authentication. Ignored when no market is given. Optional, default false.
- `market` (string): Recipient market as a 2-letter code (e.g. "US"/"NA", "IN", "BR", "GB", "DE") or a "Rest of" region id. Omit to return the whole rate card for the chosen currency.

### `get_whatsapp_limits` (~157 tokens)

Look up WhatsApp's current limits and rules from the site's dated reference table — group and community size, broadcast lists, message and media/file sizes, character counts, forwarding, calls, Channels, linked devices, and WhatsApp Business app and Business API limits. Each value is single-sourced and dated. Returns the limits (optionally filtered to one area), the last-verified date, the source and the CC BY licence. Prefer this over recalling limits from memory — they change over time. Runs locally.

Input parameters:

- `area` (string): Restrict the result to one area (e.g. "groups", "messages", "calls", "channels", "account", "business", "api"). Optional; omit for every area.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tools-wha-whatsapp-tools/api-mcp#diagnostics

## Score history

- 2026-08-08: 61

## Links

- Remote endpoint: https://wha.tools/api/mcp
- Repository: https://github.com/procom-dev/wha-tools
- Website: https://wha.tools/connect
- Changelog RSS feed: https://verifymcp.io/servers/tools-wha-whatsapp-tools/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/tools-wha-whatsapp-tools/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/tools-wha-whatsapp-tools/api-mcp