# WasapFlow Bridge

> Official WhatsApp Business API for your own CRM or SaaS: docs, numbers, messages, webhooks.

- name: com.wasapflow/bridge
- version: 1.0.1
- connection class: R0 (autonomous)
- trust: 96/100
- quality: 85/100 (new)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.wasapflow%2Fbridge
- tools: https://api.protogrid.dev/v1/servers/com.wasapflow%2Fbridge/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "bridge": {
      "type": "http",
      "url": "https://officialapi.wasapflow.com/bridge/mcp",
      "headers": {
        "x-partner-key": "${X_PARTNER_KEY}"
      }
    }
  }
}
```

Placeholders to fill: `${X_PARTNER_KEY}`.

## Trust

- hygiene: 100
- liveness: 100
- freshness: 100
- provenance: 85
- drivers: +repository +dns-namespace +website +reachable +uptime-100% +updated-3d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 85/100 (new)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 93 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 16 of 16 tools declare readOnlyHint or destructiveHint
- warn `tools.directory_hints`: 3 of 16 tools declare all four hints; missing: bridge_list_numbers (destructiveHint, idempotentHint); bridge_number_status (destructiveHint, idempotentHint); bridge_usage (destructiveHint, idempotentHint); …
- pass `tools.token_cost`: about 2,477 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`: tool history recorded for 3 of the 7 days needed

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 16, about 2,477 tokens to load them all
- tool set hash: c7e6aab5675d6de5edaad2fc1c236be3
- tools last changed: 2026-11-07T05:08:31.305Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.wasapflow/bridge.svg)](https://protogrid.dev/servers/com.wasapflow/bridge)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-11-07 `bridge_call_api` changed (inputSchema)
- 2026-11-07 `bridge_failed_webhooks` changed (description) **meaning changed**
  - before: Webhook events Bridge could not deliver to your webhook URL (with the error). Use when incoming messages are missing in the CRM.
  - after: Webhook events Bridge could not deliver to your webhook URL (with the error). Bridge retries each one automatically for 24 hours (1m, 5m, 15m, 30m, 1h, 2h, 4h, 8h, then every 8h); auto_retry shows the next attempt, and final=true means the schedule ended and the event needs bridge_retry_webhooks. Use when incoming messages or statuses are missing in the CRM.
- 2026-11-07 `bridge_send_marketing` changed (inputSchema)
- 2026-11-07 `bridge_send_template` changed (inputSchema)
- 2026-11-07 `bridge_send_text` changed (inputSchema)
- 2026-11-04 `bridge_send_marketing` added
  - 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.

Full history: https://api.protogrid.dev/v1/servers/com.wasapflow%2Fbridge/changes

## Remotes

- https://officialapi.wasapflow.com/bridge/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (16)

- `bridge_call_api`: 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.
- `bridge_connect_link`: 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.
- `bridge_docs_search`: 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.
- `bridge_docs_section`: 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.
- `bridge_failed_webhooks`: Webhook events Bridge could not deliver to your webhook URL (with the error). Bridge retries each one automatically for 24 hours (1m, 5m, 15m, 30m, 1h, 2h, 4h, 8h, then every 8h); auto_retry shows the next attempt, and final=true means the schedule ended and the event needs bridge_retry_webhooks. Use when incoming messages or statuses are missing in the CRM.
- `bridge_get_started`: 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.
- `bridge_list_numbers`: List the WhatsApp Business Accounts (client numbers) registered to this partner, with status.
- `bridge_list_templates`: List the message templates of a number with their approval status.
- `bridge_list_tickets`: List support tickets and replies status.
- `bridge_number_status`: Live status of a number from Meta: verified name, quality rating, messaging limit, name status.
- `bridge_open_ticket`: 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.
- `bridge_retry_webhooks`: Redeliver one failed webhook event (event_id) or all of them (omit event_id) after the webhook endpoint is fixed.
- `bridge_send_marketing`: 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.
- `bridge_send_template`: 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.
- `bridge_send_text`: 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.
- `bridge_usage`: Current Bridge plan: active WhatsApp numbers, slots and the monthly Bridge fee.
