WasapFlow Bridge
REMOTE · OFFICIALAPI.WASAPFLOW.COM
Official WhatsApp Business API for your own CRM or SaaS: docs, numbers, messages, webhooks.
Available components
Last scanned (2 hours ago)
Scores higher than 43% of remote servers
Reachable. Last reached 5 Nov 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 Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (bridge_call_api). See how to fix → View diagnostics → Fail
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1371 tokens (~85/item across 16 items; 16 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.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.
- 5 Nov 26 +1
- Schema quality: 1213 → 1371 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “bridge_send_marketing” functional
- 4 Nov 26 60
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 5 Nov 2026 · Probed https://officialapi.wasapflow.com/bridge/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=wasapflow.com | CN=WE1,O=Google Trust Services,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b11485660d3419580e27f3d1b567d5b3 |
| SANs: wasapflow.com, *.wasapflow.com | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of officialapi.wasapflow.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| wasapflow.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://officialapi.wasapflow.com/bridge/mcp | Verified | 200 | |
| http (plaintext) | http://officialapi.wasapflow.com/bridge/mcp | Served over HTTP | 200 |
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 →
bridge_call_api Call any Bridge API endpoint ~132
Call any WasapFlow Bridge endpoint not covered by the other tools (see bridge_docs_search for paths). Irreversible endpoints need {"confirm": true} in the body. Confirm with the user before any call that sends, deletes or changes something.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | Optional JSON body. |
| method | string | yes | – |
| path | string | yes | Path after /bridge/v1, e.g. /broadcasts or /templates/order_confirmed. |
| query | object | – | Optional query string parameters. |
| waba_id | string | – | Optional x-waba-id for number-scoped endpoints. |
No output schema declared.
No examples provided.
bridge_connect_link Create a Connect WhatsApp link ~80
Create a short-lived (30 min) link that a business opens to connect its WhatsApp number through Meta Embedded Signup (Coexistence supported). Share the returned connect_url with the business owner.
| Name | Type | Req | Description |
|---|---|---|---|
| display_name | string | – | Business name shown on the page. |
| state | string | – | Your own client id, echoed back in the onboarding webhook. |
No output schema declared.
No examples provided.
bridge_docs_search Search the Bridge docs ~76
Search the WasapFlow Bridge API reference, partner guide and changelog. Returns matching sections with a preview. Use before writing integration code. No partner key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | What to look for, e.g. "webhook signature", "send template", "coexistence", "error 131047". |
No output schema declared.
No examples provided.
bridge_docs_section Read a Bridge docs section ~84
Return the full text of one section (with its sub-sections) of the WasapFlow Bridge docs, e.g. "Verify Incoming Webhooks", "Send Template Message", "Webhook Event Payloads", "Error Codes". No partner key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| doc | string | – | Optional: which document. |
| heading | string | yes | Section heading (exact or partial). |
No output schema declared.
No examples provided.
bridge_failed_webhooks Webhooks that failed to reach your server ~43
Webhook events Bridge could not deliver to your webhook URL (with the error). Use when incoming messages are missing in the CRM.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
bridge_get_started How to integrate WasapFlow Bridge ~69
Step-by-step plan to add the official WhatsApp Business API to the user's own CRM/SaaS with WasapFlow Bridge: account, card, keys, webhook, Connect WhatsApp button, first message. Call this first when someone wants to build or connect WhatsApp. No partner key needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bridge_list_numbers List connected WhatsApp numbers ~34
List the WhatsApp Business Accounts (client numbers) registered to this partner, with status.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
bridge_list_templates List message templates ~45
List the message templates of a number with their approval status.
| Name | Type | Req | Description |
|---|---|---|---|
| waba_id | string | yes | WhatsApp Business Account ID registered to your partner account (see bridge_list_numbers). |
No output schema declared.
No examples provided.
bridge_list_tickets List support tickets ~24
List support tickets and replies status.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | – |
No output schema declared.
No examples provided.
bridge_number_status Phone number status & quality ~53
Live status of a number from Meta: verified name, quality rating, messaging limit, name status.
| Name | Type | Req | Description |
|---|---|---|---|
| waba_id | string | yes | WhatsApp Business Account ID registered to your partner account (see bridge_list_numbers). |
No output schema declared.
No examples provided.
bridge_open_ticket Open a support ticket ~119
Open a WasapFlow support ticket. Include what happened, when (with timezone), the exact error (Meta code, fbtrace_id), what was tried and the business impact.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| diagnostics | object | – | Optional raw error JSON / sample request (max 20 KB). |
| message | string | yes | Full details. |
| priority | string | – | – |
| subject | string | yes | Short summary, max 200 characters. |
| waba_id | string | – | Optional: the affected number's WABA ID. |
No output schema declared.
No examples provided.
bridge_retry_webhooks Redeliver failed webhooks ~53
Redeliver one failed webhook event (event_id) or all of them (omit event_id) after the webhook endpoint is fixed.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | – | Optional event id from bridge_failed_webhooks. |
No output schema declared.
No examples provided.
bridge_send_marketing Send a marketing template (Marketing Messages API) ~158
Send an approved MARKETING template through Meta's Marketing Messages API (quality-based delivery, marketing metrics). Not onboarded yet? Meta falls back to Cloud API unless product_policy is STRICT. This sends a real message and Meta charges for it.
| Name | Type | Req | Description |
|---|---|---|---|
| components | array | – | Optional Meta template components. |
| language | string | yes | Template language code, e.g. en_US, ms. |
| name | string | yes | Marketing template name. |
| product_policy | string | – | Optional. STRICT = never fall back to Cloud API. |
| to | string | yes | Recipient phone in international format without +, or a BSUID. |
| waba_id | string | yes | WhatsApp Business Account ID registered to your partner account (see bridge_list_numbers). |
No output schema declared.
No examples provided.
bridge_send_template Send a WhatsApp template message ~123
Send an approved template (works outside the 24-hour window). components follows the Meta Cloud API format. This sends a real message and Meta may charge for it.
| Name | Type | Req | Description |
|---|---|---|---|
| components | array | – | Optional Meta template components (header/body/button parameters). |
| language | string | yes | Template language code, e.g. en_US, ms. |
| name | string | yes | Template name. |
| to | string | yes | Recipient phone in international format without +. |
| waba_id | string | yes | WhatsApp Business Account ID registered to your partner account (see bridge_list_numbers). |
No output schema declared.
No examples provided.
bridge_send_text Send a WhatsApp text message ~109
Send a text message from a connected number. Free-form text only reaches people who messaged that number in the last 24 hours; otherwise use bridge_send_template. This sends a real message.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Message text. |
| to | string | yes | Recipient phone in international format without + (e.g. 60123456789) or a BSUID. |
| waba_id | string | yes | WhatsApp Business Account ID registered to your partner account (see bridge_list_numbers). |
No output schema declared.
No examples provided.
bridge_usage Bridge plan & usage ~24
Current Bridge plan: active WhatsApp numbers, slots and the monthly Bridge fee.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the WasapFlow Bridge MCP server?
WasapFlow Bridge is a hosted endpoint at https://officialapi.wasapflow.com/bridge/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 · officialapi.wasapflow.com
claude mcp add --transport http com-wasapflow-bridge 'https://officialapi.wasapflow.com/bridge/mcp'
What is the WasapFlow Bridge MCP server?
WasapFlow Bridge is an MCP server listed in the public MCP registry as com.wasapflow/bridge. Official WhatsApp Business API for your own CRM or SaaS: docs, numbers, messages, webhooks. This page covers its hosted endpoint (https://officialapi.wasapflow.com/bridge/mcp).
Is the WasapFlow Bridge MCP server safe to use?
WasapFlow Bridge scores 61 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 WasapFlow Bridge MCP server expose?
WasapFlow Bridge exposes 16 tools: bridge_get_started, bridge_docs_search, bridge_docs_section, bridge_list_numbers, bridge_number_status, and 11 more. Their descriptions and schemas cost roughly 1,226 tokens of context every time the server is loaded.
Does the WasapFlow Bridge MCP server require authentication?
No. We connected to WasapFlow Bridge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the WasapFlow Bridge MCP server still maintained?
WasapFlow Bridge is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.