Wapiworld WhatsApp API
REMOTE · MCP.WAPIWORLD.COM
Check your WhatsApp numbers, connection status and webhooks, and send a text when you confirm.
Available components
Last scanned (19 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Communication
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 → Why this is hard to score →
Endpoint Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2615 tokens (~217/item across 12 items; 8 tools + 4 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 Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
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.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +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.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 80. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 53 to 73. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Schema Quality & AI Usability fell 1.
- 4 Oct 26 +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.
- 2 Oct 26 +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.
- 30 Sept 26 +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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 16 Oct 2026 · Probed https://mcp.wapiworld.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.wapiworld.com | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 23 Sept 2026 | 8 Apr 2027 | RSA 2048 | SHA256-RSA | c9e4c754003352097487a78b879a4b7 |
| SANs: *.wapiworld.com, wapiworld.com | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.wapiworld.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| wapiworld.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="wapiworld", resource_metadata="https://mcp.wapiworld.com/.well-known/oauth-protected-resource", error="invalid_token", error_description="missing Bearer token"
Bearer realm="wapiworld", resource_metadata="https://mcp.wapiworld.com/.well-known/oauth-protected-resource", error="invalid_token", error_description="missing Bearer token"Protected resource metadata
| Document | https://mcp.wapiworld.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.wapiworld.com |
| Authorisation server | https://api.authrice.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.wapiworld.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.wapiworld.com/mcp | HTTPS enforced |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_instance Get WhatsApp number details ~82
Use this when someone asks about one connected WhatsApp number, such as its phone number, account name or connection health. Returns the instance's name, account name, phone number, project, status and health, or not-found. Not for message history, which this connector does not read.
| Name | Type | Req | Description |
|---|---|---|---|
| instanceId | string | yes | Instance id: 24 lowercase hexadecimal characters |
| Name | Type | Req | Description |
|---|---|---|---|
| instance | – | yes | Null when not found. QR pairing codes, instance secrets, API keys, proxy addresses, organization ids and arbitrary stored metadata are never returned. |
| status | string | yes | – |
No examples provided.
get_instance_status Check if a WhatsApp number is connected ~85
Use this when someone asks whether a WhatsApp number is connected, waiting for QR pairing, starting or offline. Returns the instance's name, raw status and a health value: ready, pairing, starting, offline or unknown (no QR codes or credentials). Not for whether a sent message was delivered.
| Name | Type | Req | Description |
|---|---|---|---|
| instanceId | string | yes | Instance id: 24 lowercase hexadecimal characters |
| Name | Type | Req | Description |
|---|---|---|---|
| found | boolean | yes | – |
| health | string | yes | ready: connected; pairing: waiting for a QR scan; starting: connecting; offline: logged out or disconnected; unknown: unrecognized state |
| instanceId | string | yes | – |
| name | – | yes | – |
| status | – | yes | – |
No examples provided.
get_message_recording_policy Check message recording settings ~89
Use this when someone asks whether Wapiworld stores the text of WhatsApp messages for a number, or how long it keeps them. Returns whether recording is on for the instance, whether the default, project or instance decided it, any lock, and the project's retention in days. Not for reading recorded messages.
| Name | Type | Req | Description |
|---|---|---|---|
| instanceId | string | yes | Instance id: 24 lowercase hexadecimal characters |
| Name | Type | Req | Description |
|---|---|---|---|
| policy | – | yes | Instance default only; chat-level exceptions are excluded. Message bodies, previews, sender names, contact identifiers, chat override keys and WhatsApp message ids are never read. |
| status | string | yes | – |
No examples provided.
list_instances List WhatsApp numbers ~138
Use this when someone asks which WhatsApp numbers they have connected to Wapiworld, or which ones are offline. Returns each instance's id, name, WhatsApp account name, phone number, connection status and health, 25 per page by default, optionally for one project (no QR codes, secrets or API keys). Not for sending a message.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | The page.nextCursor of the previous page with the same projectId; absent for the first page |
| limit | integer | – | Instances per page, from 1 to 100; defaults to 25 |
| projectId | string | – | Only this project |
| Name | Type | Req | Description |
|---|---|---|---|
| instances | array | yes | Connected WhatsApp instances. health is ready, pairing, starting, offline or unknown. QR pairing codes, instance secrets, API keys, proxy data and arbitrary stored fields are never returned. |
| page | object | yes | Pass nextCursor as cursor, with the same filters, for the next page; null on the last page |
No examples provided.
list_projects List your Wapiworld projects ~103
Use this when someone asks which Wapiworld projects they have, or a project's id is needed. Returns each project's id, name and creation and edit times, 25 per page by default, with a cursor for more. Not for their WhatsApp numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | The page.nextCursor of the previous page; absent for the first page |
| limit | integer | – | Projects per page, from 1 to 100; defaults to 25 |
| Name | Type | Req | Description |
|---|---|---|---|
| page | object | yes | Pass nextCursor as cursor, with the same filters, for the next page; null on the last page |
| projects | array | yes | Projects the session can reach; an API-key session sees only its own project. Internal organization ids and project configuration are omitted. |
No examples provided.
list_webhook_subscriptions Check webhook delivery health ~145
Use this when someone asks whether their Wapiworld webhooks are working, failing or were switched off. Returns each subscription's endpoint scheme and host, events, active state, consecutive failures and an auto-disabled flag after 20 failures, 25 per page by default. Works only with an operator OAuth session, not an API key. Not for changing a webhook.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | The page.nextCursor of the previous page with the same projectId; absent for the first page |
| limit | integer | – | Webhook subscriptions per page, from 1 to 100; defaults to 25 |
| projectId | string | – | Only this project |
| Name | Type | Req | Description |
|---|---|---|---|
| page | object | yes | Pass nextCursor as cursor, with the same filters, for the next page; null on the last page |
| webhookSubscriptions | array | yes | Delivery health per subscription; autoDisabled marks an endpoint switched off after 20 consecutive failures. The signing secret, delivery paths, queries and fragments are never returned: hook paths o… |
No examples provided.
send_message Send WhatsApp message ~173
Use this when someone asks to send a WhatsApp message from one of their Wapiworld numbers. Returns only that Wapiworld accepted the send, not proof of delivery. The message goes out immediately, each call sends another copy, and recording settings may store its text. Not for broadcasts or bulk sends.
| Name | Type | Req | Description |
|---|---|---|---|
| chatId | string | yes | Exact recipient phone number in international format (for example +1234567890) or exact WhatsApp chat id. Show it to the user before requesting confirmation. |
| content | string | yes | Exact text message to send, maximum 4096 characters. Show the complete text before confirmation. Do not send credentials, PHI, PCI cardholder data, government identifiers, or other restricted data. |
| instanceId | string | yes | Sender instance id, shown to the user before confirmation |
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | yes | Wapiworld accepted the send for transport; not proof of delivery or reading |
No examples provided.
show_project_overview Show Wapiworld project overview ~87
Use this when someone wants a quick overview or dashboard of one Wapiworld project's WhatsApp numbers. Returns an overview card with the project name, how many instances are ready, pairing, starting, offline or unknown (counting up to 100), and up to 20 instances with phone and status. Not for sending a message.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | Project id |
| Name | Type | Req | Description |
|---|---|---|---|
| instanceCount | integer | yes | – |
| instanceCountIsLowerBound | boolean | yes | – |
| instances | array | yes | Up to 20 instances. QR pairing codes, instance credentials, API keys, proxy data and arbitrary stored fields are excluded. |
| project | – | yes | – |
| statusCounts | object | yes | – |
| statusCountsAreLowerBounds | boolean | yes | – |
No examples provided.
How do I install the Wapiworld WhatsApp API MCP server?
Wapiworld WhatsApp API is a hosted endpoint at https://mcp.wapiworld.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.wapiworld.com
claude mcp add --transport http com-wapiworld-wapiworld 'https://mcp.wapiworld.com/mcp'
What is the Wapiworld WhatsApp API MCP server?
Wapiworld WhatsApp API is an MCP server listed in the public MCP registry as com.wapiworld/wapiworld. Check your WhatsApp numbers, connection status and webhooks, and send a text when you confirm. This page covers its hosted endpoint (https://mcp.wapiworld.com/mcp).
Is the Wapiworld WhatsApp API MCP server safe to use?
Wapiworld WhatsApp API scores 92 out of 100 on VerifyMCP. 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 Wapiworld WhatsApp API MCP server expose?
Wapiworld WhatsApp API exposes 8 tools: list_projects, list_instances, get_instance, get_instance_status, get_message_recording_policy, and 3 more. Their descriptions and schemas cost roughly 902 tokens of context every time the server is loaded.
Does the Wapiworld WhatsApp API MCP server require authentication?
Yes. Wapiworld WhatsApp API asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Wapiworld WhatsApp API MCP server still maintained?
Wapiworld WhatsApp API is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.