A TypeScript implementation of a simple MCP server that exposes datetime information to agentic systems and chat REPLs
Nothing to run from here
WhaTools — WhatsApp tools is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
8
tools declared
remote
at its publisher
—
calls last 7d
What it does
WhatsApp tools: wa.me links, QR codes, share widgets, phone validation, API rate card & limits.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http whatools-whatsapp-tools-mcp https://wha.tools/api/mcp
# 2 — ask your agent for something these tools do
# generate_whatsapp_link, generate_bulk_whatsapp_links, validate_phone_number and 5 more
WhaTools — WhatsApp tools costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
WHAll 1 server
wha1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http whatools-whatsapp-tools-mcp https://wha.tools/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Generate a WhatsApp click-to-chat (wa.me) link with an optional phone number and pre-filled message. Runs locally; no message is sent.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| phone | string | no | Recipient phone number in international format (digits only; optional). Omit to create a share link with no specific recipient. |
| message | string | no | The message to pre-fill in the chat (optional). |
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 variati
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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 variation |
| contacts | array | yes | Up to 500 contacts. Each needs a "phone" (international format, digits only) plus any placeholder fields as string properties. |
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 AP
| Parameter | Type | Required | Notes |
|---|---|---|---|
| phone | string | yes | The phone number to validate. International format with a leading "+" is best; otherwise also pass country. |
| country | string | no | ISO 3166-1 alpha-2 country code (e.g. "GB", "US") assumed when the number has no country code. Optional. |
Generate a scannable QR code (as an SVG) for a WhatsApp click-to-chat link with an optional phone number and pre-filled message.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| phone | string | no | Recipient phone number in international format (digits only; optional). |
| message | string | no | The message to pre-fill in the chat (optional). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The URL being shared. |
| title | string | yes | Title shown on the preview card. |
| description | string | yes | Message text shown above the card (supports *bold*, _italic_, ~strike~). |
| thumbnail | string | no | Preview image URL (optional). |
| domain | string | no | Domain label shown on the card (optional). |
| buttonText | string | no | Call-to-action button text (optional; defaults to "Share on WhatsApp"). |
| buttonPlacement | string | no | Where to place the share button relative to the card (optional). |
| includeCredit | boolean | no | Append a small "Widget by wha.tools" credit line under the widget (optional; default false). |
Estimate the monthly WhatsApp Business (Cloud) API cost under Meta's per-message pricing (in effect since 1 July 2025). Given a country/market and monthly volumes of marketing, utility, authentication and (optionally) service messages, returns an itemized breakdown and total in USD. Marketing is always billed; utility and authentication are billed with volume-tier discounts in many markets. As of
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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 | no | Monthly count of marketing template messages (promotions, offers). |
| utility | number | no | Monthly count of utility template messages (order updates, receipts, reminders). |
| authentication | number | no | Monthly count of authentication template messages (one-time passcodes). |
| service | number | no | Monthly count of service messages (free-form replies inside a customer-opened window). Optional. When given, the first 1,000 per phone number each month are free and the rest bill at the market's util |
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-internat
| Parameter | Type | Required | Notes |
|---|---|---|---|
| market | string | no | 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. |
| currency | string | no | 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 con |
| include_tiers | boolean | no | 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. |
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 a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| area | string | no | Restrict the result to one area (e.g. "groups", "messages", "calls", "channels", "account", "business", "api"). Optional; omit for every area. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install WhaTools — WhatsApp tools or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 0.85.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest60ae9860f32047a689e12ccff70a10edfa9a64ae1774223148822ca8c206d9fc
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| generate_whatsapp_link | no tags | |
| generate_bulk_whatsapp_links | no tags | |
| validate_phone_number | no tags | |
| generate_whatsapp_qr | no tags | |
| build_whatsapp_share_widget | no tags | |
| estimate_whatsapp_api_cost | no tags | |
| get_whatsapp_rates | no tags | |
| get_whatsapp_limits | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest60ae9860f32047a6
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.85.0.
0.85.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish WhaTools — WhatsApp tools can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.