PayAI MCP server

Which servers in the official MCP registry are PayAI's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-18

← Back to PayAI

Whose server it is

Registry namenetwork.payai/facilitatorverified in the MCP registry

The registry name sits under payai.network. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-18

Stateanswerschecked 2026-10-18
Tools5
Server calls itselfPayAI x402 Facilitator
Server version2.0.1
Protocol version2025-06-18

On 2026-10-18 the server answered initialize and tools/list without a sign-in. First answer in 230 ms.

Tools it offers5 tools · read 2026-10-18

get_supported
Returns the payment networks, schemes, assets, and facilitator addresses currently supported by PayAI. Use it before constructing payment requirements when you need live capability data.
verify_payment
Verifies a signed x402 payment payload against the supplied payment requirements. It checks validity but moves no funds.
settle_payment
Broadcasts the payment on-chain and moves real funds; it is idempotent per signed payload, so resubmitting the identical payload returns the recorded outcome. Treat errorReason "settlement_pending" as unresolved and call again with the…
list_discovery_resources
Lists x402-payable resources published in the PayAI Bazaar catalog. Use limit and offset to page through APIs, MCP tools, and agent services available for discovery.
get_discovery_stats
Returns aggregate statistics for the PayAI Bazaar catalog and its settlement activity. Use it for a compact view of catalog size and payment volume rather than individual resources.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "facilitator": {
      "type": "http",
      "url": "https://facilitator.payai.network/mcp"
    }
  }
}

OpenAPI spec

6 paths, read 2026-10-18. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.