WhaTools — WhatsApp tools
REMOTE · WHA.TOOLS · SCANNED AUG 8
WhatsApp tools: wa.me links, QR codes, share widgets, phone validation, API rate card & limits.
Available components
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. How we score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · wha.tools
claude mcp add --transport http tools-wha-whatsapp-tools https://wha.tools/api/mcp
[mcp_servers.tools-wha-whatsapp-tools] url = "https://wha.tools/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tools-wha-whatsapp-tools": {
"type": "remote",
"url": "https://wha.tools/api/mcp",
"enabled": true
}
}
} openclaw mcp add tools-wha-whatsapp-tools --url https://wha.tools/api/mcp --transport streamable-http
mcp_servers:
tools-wha-whatsapp-tools:
url: "https://wha.tools/api/mcp" {
"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.
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.
- 8 Aug 26 61
First indexed and scored.
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 8 Aug 2026 · Probed https://wha.tools/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=wha.tools | CN=WE1,O=Google Trust Services,C=US | 11 Jul 2026 | 9 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | e1942264ed1510660ee559a0be94d6f6 |
| SANs: wha.tools, *.wha.tools | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC secure
Validation of wha.tools. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tools. | present | 13831 | 8 | Verified |
| wha.tools. | present | 2371 | 13 | Verified |
| wha.tools. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://wha.tools/api/mcp | Verified | 200 | |
| http (plaintext) | http://wha.tools/api/mcp | HTTPS enforced | 301 | https://wha.tools/api/mcp |
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.
build_whatsapp_share_widget ~191
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Title shown on the preview card. |
| url | string | yes | The URL being shared. |
No output schema declared.
No examples provided.
estimate_whatsapp_api_cost ~280
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.
| Name | Type | Req | Description |
|---|---|---|---|
| authentication | number | – | Monthly count of authentication template messages (one-time passcodes). |
| market | string | yes | 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. |
No output schema declared.
No examples provided.
generate_bulk_whatsapp_links ~274
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contacts | array | yes | Up to 500 contacts. Each needs a "phone" (international format, digits only) plus any placeholder fields as string properties. |
| template | string | yes | 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… |
No output schema declared.
No examples provided.
generate_whatsapp_link ~87
Generate a WhatsApp click-to-chat (wa.me) link with an optional phone number and pre-filled message. Runs locally; no message is sent.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
generate_whatsapp_qr ~76
Generate a scannable QR code (as an SVG) for a WhatsApp click-to-chat link with an optional phone number and pre-filled message.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | The message to pre-fill in the chat (optional). |
| phone | string | – | Recipient phone number in international format (digits only; optional). |
No output schema declared.
No examples provided.
get_whatsapp_limits ~157
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.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | Restrict the result to one area (e.g. "groups", "messages", "calls", "channels", "account", "business", "api"). Optional; omit for every area. |
No output schema declared.
No examples provided.
get_whatsapp_rates ~335
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
validate_phone_number ~168
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166-1 alpha-2 country code (e.g. "GB", "US") assumed when the number has no country code. Optional. |
| phone | string | yes | The phone number to validate. International format with a leading "+" is best; otherwise also pass `country`. |
No output schema declared.
No examples provided.