# Celo x402 Facilitator MCP server

> Check supported assets, fees and verify signed x402 payments on Celo without moving funds.

- Listing: https://mcp.tc/i/celo-x402-facilitator
- Connect: use the server's own URL `https://api.x402.celo.org/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [Finance & Payments](https://mcp.tc/c/finance-payments)
- Vendor: Celo
- Homepage: <https://celo.org/>

## About

Read-only access to the Celo x402 facilitator. You can list the payment kinds and assets that settle on the network, read the pricing and free-credit configuration, check facilitator health, verify a signed x402 payment, and look up whether a payment authorization has been used on chain.

It runs as a hosted streamable HTTP endpoint at api.x402.celo.org/mcp. No sign-in or API key is needed. Settlement is not offered over MCP; it needs an API key and is done with POST /settle over HTTP.

## What it can do

- List supported x402 versions, schemes and networks
- Read settleable assets, fee model and free-credit allowances
- Check facilitator health
- Verify a signed x402 payment without moving funds
- Check whether a payment authorization is unspent, consumed or expired

## Tools (5)

- `get_supported`: List the x402 version, scheme and network kinds and extensions the facilitator handles. (read-only)
- `get_config`: Show settleable assets, pricing model, gas fallback and free-credit allowances. (read-only)
- `get_health`: Report whether the facilitator is answering. (read-only)
- `verify_payment`: Check a signed x402 payment's signature, amount, balance and simulation; moves no funds. (read-only)
- `payment_status`: Report whether a payment authorization is unspent, consumed or expired on chain. (read-only)

## Example prompts

- "Which payment kinds and assets does the Celo x402 facilitator support?"
- "What fee does the Celo facilitator charge on payments?"
- "Verify this signed x402 payment against its requirements."
- "Has this payment authorization been used on chain yet?"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http celo-x402-facilitator https://api.x402.celo.org/mcp
```

2. Start Claude Code and type `/mcp`. **celo-x402-facilitator** should show as connected.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Celo x402 Facilitator** and paste this URL:

```url
https://api.x402.celo.org/mcp
```

3. Click **Add**. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Celo%20x402%20Facilitator&connectorUrl=https%3A%2F%2Fapi.x402.celo.org%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://api.x402.celo.org/mcp` and click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://api.x402.celo.org/mcp` as the server URL, then for authentication choose **No authentication**.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=celo-x402-facilitator&config=eyJ1cmwiOiJodHRwczovL2FwaS54NDAyLmNlbG8ub3JnL21jcCJ9>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "celo-x402-facilitator": {
      "url": "https://api.x402.celo.org/mcp"
    }
  }
}
```

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=celo-x402-facilitator&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fapi.x402.celo.org%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"celo-x402-facilitator","type":"http","url":"https://api.x402.celo.org/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

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

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "celo-x402-facilitator": {
      "serverUrl": "https://api.x402.celo.org/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add celo-x402-facilitator --url https://api.x402.celo.org/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.celo-x402-facilitator]
url = "https://api.x402.celo.org/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http celo-x402-facilitator https://api.x402.celo.org/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

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

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://api.x402.celo.org/mcp`.

## Recent changes

- 2026-10-27 23:44 UTC: Tracking started: 5 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/celo-x402-facilitator#history (Atom feed: https://mcp.tc/i/celo-x402-facilitator/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 0.1.0
- MCP protocol version: 2025-11-25
- Last checked: 2026-11-15 (reachable)
- Listed: 2026-10-27
- Updated: 2026-10-27

---
Source: https://mcp.tc/i/celo-x402-facilitator (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report