Koskamo

PayAI x402 Facilitator MCP

This official MCP server allows AI agents to verify and settle stablecoin micropayments over HTTP using the x402 protocol. It supports browsing a catalog of x402-payable resources, checking supported payment networks, and executing on-chain settlements for services like APIs and tools.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

PayAI x402 Facilitator MCP logo, by PayAIVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by PayAI
MCP endpoint (Streamable HTTP)
https://facilitator.payai.network/mcp
Vendor documentation

What its tools do

5 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

5 of 5 have a description · 0 of 5 declare behavior hints · 0 of 3 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to payai.network ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Verify and settle stablecoin micropayments for API requests
  • Browse the PayAI Bazaar catalog of x402-payable resources
  • Check which blockchain networks and payment schemes are live

Source and maintenance

Vendor evidenceRegistry 2.0.1

Protocol and capabilities

Server
PayAI x402 Facilitator 2.0.1
MCP protocol negotiated in check
2025-06-18
Tools
5 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

This server exposes the PayAI x402 facilitator for checking supported payment kinds, verifying signed payments, settling them, and browsing Bazaar discovery data. settle_payment broadcasts a real on-chain transaction and moves funds; it is idempotent per signed payload, so resubmitting an identical payload returns its recorded outcome. GET-backed tools are free and unauthenticated.

Tools

5 advertised

get_supported — Get supported payment kinds
Advertised by the server during the last successful anonymous check.

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.

get_supported input schema
{
  "type": "object",
  "required": [],
  "properties": {},
  "additionalProperties": false
}
verify_payment — Verify a signed x402 payment
Advertised by the server during the last successful anonymous check.

Verifies a signed x402 payment payload against the supplied payment requirements. It checks validity but moves no funds.

verify_payment input schema
{
  "type": "object",
  "required": [
    "paymentPayload",
    "paymentRequirements"
  ],
  "properties": {
    "x402Version": {
      "enum": [
        1,
        2
      ],
      "type": "integer"
    },
    "paymentPayload": {
      "type": "object"
    },
    "serverExtensions": {
      "type": "object"
    },
    "paymentRequirements": {
      "type": "object"
    }
  },
  "additionalProperties": false
}
settle_payment — Settle a signed x402 payment
Advertised by the server during the last successful anonymous check.

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 identical arguments to poll.

settle_payment input schema
{
  "type": "object",
  "required": [
    "paymentPayload",
    "paymentRequirements"
  ],
  "properties": {
    "x402Version": {
      "enum": [
        1,
        2
      ],
      "type": "integer"
    },
    "paymentPayload": {
      "type": "object"
    },
    "serverExtensions": {
      "type": "object"
    },
    "paymentRequirements": {
      "type": "object"
    }
  },
  "additionalProperties": false
}
list_discovery_resources — List Bazaar discovery resources
Advertised by the server during the last successful anonymous check.

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.

list_discovery_resources input schema
{
  "type": "object",
  "required": [],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 1000,
      "minimum": 1
    },
    "offset": {
      "type": "integer",
      "minimum": 0
    }
  },
  "additionalProperties": false
}
get_discovery_stats — Get Bazaar discovery statistics
Advertised by the server during the last successful anonymous check.

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.

get_discovery_stats input schema
{
  "type": "object",
  "required": [],
  "properties": {},
  "additionalProperties": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
329 ms
95th percentile latency
329 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 329 ms · metadata changed · 5 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http payai-x402-facilitator-mcp https://facilitator.payai.network/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add payai-x402-facilitator-mcp --url https://facilitator.payai.network/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable payai-x402-facilitator-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "payai-x402-facilitator-mcp": {
      "url": "https://facilitator.payai.network/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "payai-x402-facilitator-mcp": {
      "type": "streamableHttp",
      "url": "https://facilitator.payai.network/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start payai-x402-facilitator-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "payai-x402-facilitator-mcp": {
      "type": "http",
      "url": "https://facilitator.payai.network/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http payai-x402-facilitator-mcp https://facilitator.payai.network/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://facilitator.payai.network/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "payai-x402-facilitator-mcp": {
      "serverUrl": "https://facilitator.payai.network/mcp"
    }
  }
}

Let your agent find its tools

Find servers like PayAI x402 Facilitator MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run PayAI x402 Facilitator MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing