PayAI x402 Facilitator
REMOTE · FACILITATOR.PAYAI.NETWORK
Verify and settle x402 stablecoin payments; browse the PayAI Bazaar of x402-payable resources.
Available components
Last scanned (8 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 367 tokens (~73/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Sept 26 0
- Server version: 2.0.0 → 2.0.1 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- Stability: 0.97 → pass security
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 28 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://facilitator.payai.network/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=facilitator.payai.network | CN=YR2,O=Let's Encrypt,C=US | 11 Sept 2026 | 10 Dec 2026 | RSA 2048 | SHA256-RSA | 685bcc912decbf70a49ad1faa0ee1460490 |
| SANs: facilitator.payai.network | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of facilitator.payai.network. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| network. | present | 11416, 40414 | 8, 8 | Verified |
| payai.network. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://facilitator.payai.network/mcp | Verified | 200 | |
| http (plaintext) | http://facilitator.payai.network/mcp | HTTPS enforced | 308 | https://facilitator.payai.network/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_discovery_stats Get Bazaar discovery statistics ~41
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_supported Get supported payment kinds ~39
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_discovery_resources List Bazaar discovery resources ~57
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
settle_payment Settle a signed x402 payment ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| paymentPayload | object | yes | – |
| paymentRequirements | object | yes | – |
| serverExtensions | object | – | – |
| x402Version | integer | – | – |
No output schema declared.
No examples provided.
verify_payment Verify a signed x402 payment ~63
Verifies a signed x402 payment payload against the supplied payment requirements. It checks validity but moves no funds.
| Name | Type | Req | Description |
|---|---|---|---|
| paymentPayload | object | yes | – |
| paymentRequirements | object | yes | – |
| serverExtensions | object | – | – |
| x402Version | integer | – | – |
No output schema declared.
No examples provided.
How do I install the PayAI x402 Facilitator MCP server?
PayAI x402 Facilitator is a hosted endpoint at https://facilitator.payai.network/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.
remote · facilitator.payai.network
claude mcp add --transport http network-payai-facilitator 'https://facilitator.payai.network/mcp'
What is the PayAI x402 Facilitator MCP server?
PayAI x402 Facilitator is an MCP server listed in the public MCP registry as network.payai/facilitator. Verify and settle x402 stablecoin payments; browse the PayAI Bazaar of x402-payable resources. This page covers its hosted endpoint (https://facilitator.payai.network/mcp).
Is the PayAI x402 Facilitator MCP server safe to use?
PayAI x402 Facilitator scores 76 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 PayAI x402 Facilitator MCP server expose?
PayAI x402 Facilitator exposes 5 tools: get_supported, verify_payment, settle_payment, list_discovery_resources, get_discovery_stats. Their descriptions and schemas cost roughly 293 tokens of context every time the server is loaded.
Does the PayAI x402 Facilitator MCP server require authentication?
No. We connected to PayAI x402 Facilitator without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PayAI x402 Facilitator MCP server still maintained?
PayAI 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.