A MCP server for the Ankr Advanced API
Free
Nothing to run from here
Wbmcp 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.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
Production-ready MCP server for WhatsApp Business Cloud API automation from AI clients
Quickstart
# 1 — run it from where its publisher ships it
npx -y wbmcp
# 2 — ask your agent something
> Production-ready MCP server for WhatsApp Business Cloud API automation from AI clients
Wbmcp is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
SAAll 1 server
saravanaspar1 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. This one runs on your machine: your client starts Wbmcp as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add wbmcp -- npx -y wbmcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
61 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.
Checks configured WhatsApp Cloud API access by reading the configured phone number.
Takes no parameters.
Example callreturns →
Reads metadata for the configured WhatsApp Business Account.
Takes no parameters.
Example callreturns →
Reads metadata for the configured WhatsApp Business phone number.
Takes no parameters.
Example callreturns →
Lists phone numbers attached to the configured WhatsApp Business Account.
Takes no parameters.
Example callreturns →
Reads the configured WhatsApp Business profile.
Takes no parameters.
Example callreturns →
Reads WhatsApp conversation analytics for the configured WhatsApp Business Account.
Takes no parameters.
Example callreturns →
Reads WhatsApp template analytics for the configured WhatsApp Business Account.
Takes no parameters.
Example callreturns →
Lists commerce catalogs owned by the configured business or supplied business ID.
Takes no parameters.
Example callreturns →
Reads metadata for one commerce catalog.
Takes no parameters.
Example callreturns →
Lists products in a commerce catalog.
Takes no parameters.
Example callreturns →
Reads one commerce catalog product.
Takes no parameters.
Example callreturns →
Creates one commerce catalog product. Requires dangerous tools to be enabled.
Takes no parameters.
Example callreturns →
Updates one commerce catalog product. Requires dangerous tools to be enabled.
Takes no parameters.
Example callreturns →
Deletes one commerce catalog product. Requires dangerous tools to be enabled.
Takes no parameters.
Example callreturns →
Lists WhatsApp Flows for the configured WhatsApp Business Account.
Takes no parameters.
Example callreturns →
Reads one WhatsApp Flow by ID.
Takes no parameters.
Example callreturns →
Creates a WhatsApp Flow. Requires dangerous tools to be enabled.
Takes no parameters.
Example callreturns →
Updates WhatsApp Flow metadata. Requires dangerous tools to be enabled.
Takes no parameters.
Example callreturns →
Updates a WhatsApp Flow JSON asset. Requires dangerous tools to be enabled.
Takes no parameters.
Example callreturns →
Publishes one WhatsApp Flow. Requires dangerous tools to be enabled.
Takes no parameters.
Example callreturns →
Deprecates one WhatsApp Flow. Requires dangerous tools to be enabled.
Takes no parameters.
Example callreturns →
Deletes one WhatsApp Flow. Requires dangerous tools to be enabled.
Takes no parameters.
Example callreturns →
Reads WhatsApp media metadata by Meta media ID. This does not download media to disk.
Takes no parameters.
Example callreturns →
Deletes uploaded WhatsApp media by Meta media ID. Requires dangerous tools to be enabled.
Takes no parameters.
Example callreturns →
Sends one free-form WhatsApp text message to one E.164 recipient. Use dryRun: true to preview without sending. Requires dangerous tools to be enabled and may require confirm: true.
Takes no parameters.
Example callreturns →
Sends one approved WhatsApp template message. Use this for cold contacts or outside the 24-hour customer-service window. Use dryRun: true to preview without sending.
Takes no parameters.
Example callreturns →
Sends one WhatsApp image message by media ID or HTTPS media URL. Use dryRun: true to preview without sending.
Takes no parameters.
Example callreturns →
Sends one WhatsApp document message by media ID or HTTPS media URL. Use dryRun: true to preview without sending.
Takes no parameters.
Example callreturns →
Sends one WhatsApp audio message by media ID or HTTPS media URL. Use dryRun: true to preview without sending.
Takes no parameters.
Example callreturns →
Sends one WhatsApp video message by media ID or HTTPS media URL. Use dryRun: true to preview without sending.
Takes no parameters.
Example callreturns →
Sends one emoji reaction to a WhatsApp message. Use dryRun: true to preview without sending.
Takes no parameters.
Example callreturns →
Sends one WhatsApp sticker message by media ID or HTTPS media URL. Use dryRun: true to preview without sending.
Takes no parameters.
Example callreturns →
Sends one WhatsApp location message to one E.164 recipient. Use dryRun: true to preview without sending.
Takes no parameters.
Example callreturns →
Sends one WhatsApp contact card message to one E.164 recipient. Use dryRun: true to preview without sending.
Takes no parameters.
Example callreturns →
Sends one WhatsApp interactive button message with up to three buttons. Use dryRun: true to preview without sending.
Takes no parameters.
Example callreturns →
Sends one WhatsApp interactive list message to one E.164 recipient. Use dryRun: true to preview without sending.
Takes no parameters.
Example callreturns →
Sends one WhatsApp single-product commerce message. Use dryRun: true to preview without sending.
Takes no parameters.
Example callreturns →
Sends one WhatsApp multi-product commerce message. Use dryRun: true to preview without sending.
Takes no parameters.
Example callreturns →
Sends one WhatsApp Flow interactive message. Use dryRun: true to preview without sending.
Takes no parameters.
Example callreturns →
Marks one inbound WhatsApp message as read. Requires dangerous tools and may require confirm: true.
Takes no parameters.
Example callreturns →
Requests a WhatsApp phone number verification code. Requires dangerous tools to be enabled.
Takes no parameters.
Example callreturns →
Verifies a WhatsApp phone number code. Requires dangerous tools to be enabled.
Takes no parameters.
Example callreturns →
Registers a WhatsApp Cloud API phone number with a two-step PIN. Requires dangerous tools to be enabled.
Takes no parameters.
Example callreturns →
Deregisters a WhatsApp Cloud API phone number. Requires dangerous tools to be enabled.
Takes no parameters.
Example callreturns →
Sets the two-step verification PIN for a WhatsApp phone number. Requires dangerous tools to be enabled.
Takes no parameters.
Example callreturns →
Reads settings for the configured or supplied WhatsApp phone number.
Takes no parameters.
Example callreturns →
Updates settings for the configured or supplied WhatsApp phone number. Requires dangerous tools to be enabled.
Takes no parameters.
Example callreturns →
Updates externally visible WhatsApp Business profile fields. Requires dangerous tools to be enabled.
Takes no parameters.
Example callreturns →
Redacts tokens, phone numbers, message bodies, and sensitive URL query strings from a debug payload before sharing logs with humans or AI agents.
Takes no parameters.
Example callreturns →
Locally validates strict E.164 phone number format and returns only a masked representation.
Takes no parameters.
Example callreturns →
Explains read versus dangerous WhatsApp MCP tool classifications, including whether a tool is enabled, requires confirmation, or supports dry-run preview.
Takes no parameters.
Example callreturns →
Lists registered WhatsApp MCP tools with group, permission, read-only status, enabled status, confirmation requirement, and dry-run support.
Takes no parameters.
Example callreturns →
Returns recommended system-prompt snippets that help AI agents use WBMCP safely with previews, confirmations, and template fallback behavior.
Takes no parameters.
Example callreturns →
Lists message templates for the configured WhatsApp Business Account.
Takes no parameters.
Example callreturns →
Reads one WhatsApp message template by template ID.
Takes no parameters.
Example callreturns →
Creates a WhatsApp message template for Meta review. Requires dangerous tools to be enabled.
Takes no parameters.
Example callreturns →
Deletes a WhatsApp message template by name and optional template ID. Requires dangerous tools to be enabled.
Takes no parameters.
Example callreturns →
Locally validates a template send payload without sending a message or calling Meta.
Takes no parameters.
Example callreturns →
Lists apps subscribed to the configured WhatsApp Business Account webhooks.
Takes no parameters.
Example callreturns →
Subscribes the current app to WhatsApp Business Account webhooks. Requires dangerous tools to be enabled.
Takes no parameters.
Example callreturns →
Unsubscribes the current app from WhatsApp Business Account webhooks. Requires dangerous tools to be enabled.
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Wbmcp costs nothing to install and nothing to call, 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: $8.42
$16.58 left
ATrust score 100 / 100
Release 0.1.3 · scanned 25 Aug 2026
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 score100
Findings1 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digesta156c44b69ea0bad5220ca065dd6008377034f8fa2300b1704d82aa9c739c392
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
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 |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
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 digesta156c44b69ea0bad
Scanned2026-08-25
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
Pinned to 0.1.3 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
0.1.3
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Wbmcp in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
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 an account with 50 real tool calls against it.