_ registry / mcp streamable-http · checked 51m ago

wasapflow-bridge

https://officialapi.wasapflow.com

Registry code: 8e45bc8cc567f2c8

api record

WasapFlow Bridge gives your own SaaS or CRM the official WhatsApp Business API (Meta Cloud API) without becoming a Meta Tech Provider. Pricing: $10 USD/month per 3 WhatsApp Business Accounts; Meta bills message charges directly.

Use bridge_get_started first when helping someone integrate. Use bridge_docs_search / bridge_docs_section to read the API reference before writing integration code — the docs are always current. Tools that call the live API need a partner key (header x-partner-key); without one they explain how to get it. Base URL for code you write:…

endpoint
https://officialapi.wasapflow.com/bridge/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is wasapflow-bridge live?
Yes — it answered the hub's last check (checked 51m ago). It answered 100% of checks over the last 30 days.
Is wasapflow-bridge free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does wasapflow-bridge have?
15 tools: bridge_number_status, bridge_send_template, bridge_docs_search, bridge_docs_section, bridge_connect_link, bridge_send_text, bridge_list_templates, bridge_retry_webhooks, ….
Is wasapflow-bridge safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
546ms

last good check

priced tools
0

of 15 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 15 tools
1 open2 auth-required 12 never probed 3 of 15 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • bridge_get_started open 51m ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • bridge_failed_webhooks auth-required 51m ago

    Webhook events Bridge could not deliver to your webhook URL (with the error). Use when incoming messages are missing in the CRM.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 50,
      "maximum": 200,
      "minimum": 1
    }
  }
}
    arguments 11 lines
  • bridge_list_numbers auth-required 51m ago

    List the WhatsApp Business Accounts (client numbers) registered to this partner, with status.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 50,
      "maximum": 200,
      "minimum": 1
    }
  }
}
    arguments 11 lines
  • bridge_number_status unknown never probed

    Live status of a number from Meta: verified name, quality rating, messaging limit, name status.

    mcp-tool

    {
  "type": "object",
  "required": [
    "waba_id"
  ],
  "properties": {
    "waba_id": {
      "type": "string",
      "description": "WhatsApp Business Account ID registered to your partner account (see bridge_list_numbers)."
    }
  }
}
    arguments 12 lines
  • bridge_send_template unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "waba_id",
    "to",
    "name",
    "language"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "Recipient phone in international format without +."
    },
    "name": {
      "type": "string",
      "description": "Template name."
    },
    "waba_id": {
      "type": "string",
      "description": "WhatsApp Business Account ID registered to your partner account (see bridge_list_numbers)."
    },
    "language": {
      "type": "string",
      "description": "Template language code, e.g. en_US, ms."
    },
    "components": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "description": "Optional Meta template components (header/body/button parameters)."
    }
  }
}
    arguments 34 lines
  • bridge_docs_search unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "What to look for, e.g. \"webhook signature\", \"send template\", \"coexistence\", \"error 131047\"."
    }
  }
}
    arguments 12 lines
  • bridge_docs_section unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "heading"
  ],
  "properties": {
    "doc": {
      "enum": [
        "api",
        "guide",
        "changelog"
      ],
      "type": "string",
      "description": "Optional: which document."
    },
    "heading": {
      "type": "string",
      "description": "Section heading (exact or partial)."
    }
  }
}
    arguments 21 lines
  • bridge_connect_link unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "state": {
      "type": "string",
      "description": "Your own client id, echoed back in the onboarding webhook."
    },
    "display_name": {
      "type": "string",
      "description": "Business name shown on the page."
    }
  }
}
    arguments 13 lines
  • bridge_send_text unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "waba_id",
    "to",
    "text"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "Recipient phone in international format without + (e.g. 60123456789) or a BSUID."
    },
    "text": {
      "type": "string",
      "description": "Message text."
    },
    "waba_id": {
      "type": "string",
      "description": "WhatsApp Business Account ID registered to your partner account (see bridge_list_numbers)."
    }
  }
}
    arguments 22 lines
  • bridge_list_templates unknown never probed

    List the message templates of a number with their approval status.

    mcp-tool

    {
  "type": "object",
  "required": [
    "waba_id"
  ],
  "properties": {
    "waba_id": {
      "type": "string",
      "description": "WhatsApp Business Account ID registered to your partner account (see bridge_list_numbers)."
    }
  }
}
    arguments 12 lines
  • bridge_retry_webhooks unknown never probed

    Redeliver one failed webhook event (event_id) or all of them (omit event_id) after the webhook endpoint is fixed.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "event_id": {
      "type": "string",
      "description": "Optional event id from bridge_failed_webhooks."
    }
  }
}
    arguments 9 lines
  • bridge_usage unknown never probed

    Current Bridge plan: active WhatsApp numbers, slots and the monthly Bridge fee.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • bridge_open_ticket unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "subject",
    "message"
  ],
  "properties": {
    "message": {
      "type": "string",
      "description": "Full details."
    },
    "subject": {
      "type": "string",
      "description": "Short summary, max 200 characters."
    },
    "waba_id": {
      "type": "string",
      "description": "Optional: the affected number's WABA ID."
    },
    "category": {
      "enum": [
        "technical",
        "billing",
        "onboarding",
        "other"
      ],
      "type": "string"
    },
    "priority": {
      "enum": [
        "normal",
        "high",
        "urgent"
      ],
      "type": "string"
    },
    "diagnostics": {
      "type": "object",
      "description": "Optional raw error JSON / sample request (max 20 KB)."
    }
  }
}
    arguments 42 lines
  • bridge_list_tickets unknown never probed

    List support tickets and replies status.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "status": {
      "enum": [
        "open",
        "replied",
        "closed"
      ],
      "type": "string"
    }
  }
}
    arguments 13 lines
  • bridge_call_api unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "method",
    "path"
  ],
  "properties": {
    "body": {
      "type": "object",
      "description": "Optional JSON body."
    },
    "path": {
      "type": "string",
      "description": "Path after /bridge/v1, e.g. /broadcasts or /templates/order_confirmed."
    },
    "query": {
      "type": "object",
      "description": "Optional query string parameters."
    },
    "method": {
      "enum": [
        "GET",
        "POST",
        "PUT",
        "PATCH",
        "DELETE"
      ],
      "type": "string"
    },
    "waba_id": {
      "type": "string",
      "description": "Optional x-waba-id for number-scoped endpoints."
    }
  }
}
    arguments 35 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 8e45bc8cc567f2c8.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8e45bc8cc567f2c8/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/8e45bc8cc567f2c8/badge.svg)](https://brick.blue/agent/8e45bc8cc567f2c8?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.