Celo x402 Facilitator

org.celoPublished by celo.orgOfficial publisherv1.0.0Updated Oct 30, 2026

Check supported assets and verify x402 payments on Celo

The publisher's own server: Celo Docs

VerifiedStreamable HTTPWeb executableFinanceDeveloper Tools

Overview

AI-generated overview

Read-only access to the Celo x402 facilitator: check supported payment kinds and assets, verify signed x402 payments, and look up on-chain authorization status.

What you can do
  • Look up supported payment kinds, schemes, networks and extensions
  • Inspect settleable assets, EIP-712 domain values, pricing model, gas fallback and free-credit allowances
  • Check whether the facilitator host is answering
  • Verify a signed x402 payment against its requirements (signature, amount, balance, simulation) without moving funds
  • Check whether a signed payment authorization is unspent, consumed or expired on chain
When to use it
Useful when building or debugging x402 payment flows on Celo and you want an assistant to confirm which assets and payment kinds settle, validate a signed payment before submitting it, or check whether an authorization was already used after a lost settle reply.
Requirements
A remote streamable HTTP endpoint at api.x402.celo.org; no package, account, API key or environment variable is declared. Network access to that host is required.
Before you install
Verification spends the same per-IP allowance as the HTTP verify endpoint, so repeated checks can be rate-limited. Settlement is not available over MCP and requires an API key over HTTP. An unspent status is not final: the authorization can still be used until validBefore. Payment details and addresses are sent to the facilitator host.

Installation

In SourceWeft

  1. Open Celo x402 Facilitator in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/org.celo%2Fx402-facilitator/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "celo-x402-facilitator": {
      "type": "http",
      "url": "https://api.x402.celo.org/mcp"
    }
  }
}

Tools

5

get_supported

Supported payment kinds

The (x402Version, scheme, network) kinds and extensions this facilitator verifies and settles. Same answer as GET /supported.

Takes no parameters.

get_config

Assets, fee and free credits

Every settleable asset with its address, decimals, transfer method and EIP-712 domain values, plus the pricing model (gas at cost, plus a fee in basis points on the payment value when the asset has a USD price), the gas fallback and the free-credit allowances. Same answer as GET /api/config.

Takes no parameters.

get_health

Facilitator health

Whether the facilitator behind this host is answering. Same answer as GET /health.

Takes no parameters.

verify_payment

Verify an x402 payment

Check a signed x402 payment against its requirements: signature, amount, balance and simulation. Moves no funds. Same answer as POST /verify, and it spends the same per-IP allowance.

Parametersx402VersionpaymentPayloadrequiredpaymentRequirementsrequired

payment_status

Has an authorization been used?

Whether a signed payment authorization has been used on chain, for a client whose settle reply was lost. Answers unspent, consumed or expired from the chain (EIP-3009 authorizationState, or the Permit2 nonce bitmap). unspent is not final: the authorization can still be used until validBefore, and a settlement already in flight reads as unspent here. Only consumed and expired are final; expired is only reported 5 s after validBefore, so a payment still in flight is not called final. The settled and pending states need the owning API key and are only served over HTTP. Same answer as GET /settle/status, and it spends the same per-IP allowance.

ParametersassetrequirednoncerequiredpayerrequiredvalidBefore

Version history

1
  1. v1.0.0LatestOct 30, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Celo integrations

Celo Docs

org.celoOfficial publisher

Remote MCP server that lets an assistant search and read the public Celo developer documentation and report documentation problems.

Streamable HTTPWeb executable
Knowledge & Memory3 toolsOct 30, 2026

Celo MCP Server

org.celo

Read-only MCP server for the Celo blockchain: lets an assistant look up blocks, transactions, token balances, governance proposals, staking data and request…

STDIODesktop only
Finance17 toolsOct 30, 2026