# Celo x402 Facilitator (remote · api.x402.celo.org)

Check supported assets and verify x402 payments on Celo

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.x402.celo.org`: 77/100 (this document), [markdown](https://verifymcp.io/servers/org-celo-x402-facilitator/api.md), [page](https://verifymcp.io/servers/org-celo-x402-facilitator/api)

## Channel facts

- Endpoint: `https://api.x402.celo.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 560 tokens (~112/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Celo x402 Facilitator MCP server?

Celo x402 Facilitator is a hosted endpoint at https://api.x402.celo.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-celo-x402-facilitator": {
      "type": "remote",
      "url": "https://api.x402.celo.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-celo-x402-facilitator --url 'https://api.x402.celo.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-celo-x402-facilitator:
    url: "https://api.x402.celo.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "org-celo-x402-facilitator": {
      "Transport": "http",
      "Url": "https://api.x402.celo.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-celo-x402-facilitator -t streamable-http -u 'https://api.x402.celo.org/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-27 (score 73)

First indexed and scored.

## MCP tools (5)

### `get_supported` (~34 tokens)

Supported payment kinds

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

### `get_config` (~72 tokens)

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.

### `get_health` (~24 tokens)

Facilitator health

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

### `verify_payment` (~97 tokens)

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.

Input parameters:

- `paymentPayload` (object, required): The PaymentPayload the buyer signed.
- `paymentRequirements` (object, required): The PaymentRequirements the resource server stated.
- `x402Version` (integer): x402 protocol version of the payload, e.g. 2.

### `payment_status` (~247 tokens)

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.

Input parameters:

- `asset` (string, required): Token address the payment was signed for.
- `nonce` (string, required): EIP-3009: the 32-byte hex nonce. Permit2: the nonce as a decimal or 0x-hex uint256.
- `payer` (string, required): Address that signed the authorization.
- `validBefore` (integer): Optional. The authorization's validBefore (Permit2: deadline), in unix seconds, so an unused one more than 5 s past it reads as expired.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-celo-x402-facilitator/api#diagnostics

## Score history

- 2026-11-05: 77
- 2026-11-04: 77
- 2026-11-03: 76
- 2026-11-02: 76
- 2026-11-01: 75
- 2026-10-31: 75
- 2026-10-30: 74
- 2026-10-29: 74
- 2026-10-28: 73
- 2026-10-27: 73

## Common questions

### What is the Celo x402 Facilitator MCP server?

Celo x402 Facilitator is an MCP server listed in the public MCP registry as org.celo/x402-facilitator. Check supported assets and verify x402 payments on Celo. This page covers its hosted endpoint (https://api.x402.celo.org/mcp).

### Is the Celo x402 Facilitator MCP server safe to use?

Celo x402 Facilitator scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Celo x402 Facilitator MCP server expose?

Celo x402 Facilitator exposes 5 tools: get_supported, get_config, get_health, verify_payment, payment_status. Their descriptions and schemas cost roughly 474 tokens of context every time the server is loaded.

### Does the Celo x402 Facilitator MCP server require authentication?

No. We connected to Celo x402 Facilitator without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Celo x402 Facilitator MCP server still maintained?

Celo x402 Facilitator is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Celo x402 Facilitator MCP server?

VerifyMCP ran 13 checks on Celo x402 Facilitator, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.x402.celo.org/mcp
- Changelog RSS feed: https://verifymcp.io/servers/org-celo-x402-facilitator/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-celo-x402-facilitator/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/org-celo-x402-facilitator/api.json
- HTML version of this page: https://verifymcp.io/servers/org-celo-x402-facilitator/api