
x402 Discovery MCP
io.github.rplryanPublished by GitHub account rplryanv1.2.3Updated Oct 24, 2026
Discover x402 APIs by capability, price & trust. Powered by x402Scout.
Overview
Connects an assistant to the x402Scout catalog of x402-payable APIs, so it can search services, check health and trust, and route paid calls.
- What you can do
- Search the x402 service catalog by keyword, category and maximum price, with quality signals per entry
- Check a service's live uptime and latency, and read its ERC-8004 trust score and reputation signals
- Run a compliance scan on a service URL, including live config and mismatch detection
- Register a new x402 service in the catalog
- Route an intent to a matching service and execute the x402 payment, or pay a known service URL directly
- Review the agent's spend log and budget status
- When to use it
- Useful when an assistant needs to find and evaluate x402-payable APIs before calling them, or when you want it to discover, pay for and audit paid API calls autonomously within a budget.
- Requirements
- A remote endpoint (the relay is hosted at x402-scout-relay.onrender.com); the README also documents Docker and npx install options for the discovery server. No authentication, environment variables or headers are declared. Paid tools require an x402 payment header and USDC on Base.
Installation
In SourceWeft
- Open x402 Discovery MCP in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via SSE. 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/io.github.rplryan%2Fx402-discovery-mcp/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"x402-discovery": {
"type": "sse",
"url": "https://x402-scout-relay.onrender.com/sse"
}
}
}README
x402 Service Discovery MCP Server
⭐ Star to help others find this — if x402Scout has saved you time, a star helps other developers find it
The community-built Bazaar for the x402 agentic economy — a continuously growing catalog of live services with real-time quality signals, facilitator-compatibility checks, and ERC-8004 trust scoring. The discovery layer that Coinbase's own PROJECT-IDEAS.md asked the community to build.
[MCP Registry] [Smithery Score] [API Status] [Services Indexed] [scout_relay] [x402scout CLI] [ScoutGate] [License: MIT]
ScoutGate — Instant x402 API Monetization
Wrap any existing API in x402 payments in under 2 minutes — no protocol knowledge required
The x402 ecosystem's biggest friction point has been supply-side: getting an API behind x402 payments requires understanding EIP-712 headers, facilitator registration, and settlement logic. ScoutGate removes all of it.
That's it. Your API is now x402-enabled, auto-listed in x402Scout, and settling on Base mainnet in real USDC. ScoutGate handles facilitator integration, EIP-712 verification, and settlement.
Fee model: 2% per transaction (min $0.002). Live at: https://x402-scoutgate.onrender.com | Register your API
Terminal CLI — x402scout
Search the full x402 service catalog from your terminal
See cli/README.md for full usage.
scout_relay — Autonomous Payment Router
Route, execute, and audit x402 payments in a single call
Where the Discovery MCP finds what to call, scout_relay handles calling it — discovering the best service, making the x402 payment, retrying on failure, and returning the result. One call. Fully autonomous.
4 MCP tools — add to any MCP client:
Fee model: max($0.003, 2.5% of downstream transaction value) per routed call.
Placement bids: Providers can register routing priority bids at POST /placement/bid (x402-gated, $0.01 registration fee). Bids are used as tiebreakers after trust-score filtering — merit first, always.
Live at: https://x402-scout-relay.onrender.com
What This Is (30 seconds)
x402 is Coinbase's HTTP-native micropayment standard for the agentic web. An AI agent hits an endpoint, gets an HTTP 402 challenge, pays with USDC on Base, and receives data — no API keys, no subscriptions, pure machine-to-machine.
The problem: Hundreds of x402-payable services exist across the ecosystem. The official x402.org catalog lists names. That's it. No uptime data. No latency scores. No facilitator-compatibility flags. No trust signals. An agent has no way to know which services are actually live, trustworthy, or compatible with its payment flow.
This MCP server solves it. Connect any Claude, Cursor, or Windsurf agent directly to the x402 Service Discovery API — a continuously-updated catalog with real quality signals on every entry. Find services, check health, verify facilitator compatibility, and register new endpoints — all from inside your AI workflow.
MCP Tools (5 discovery + 4 relay = 9 total)
Discovery Tools
Relay Tools (via scout_relay)
Quickstart — 30 Seconds to Discovery
Option A: Docker (recommended)
Add to your claude_desktop_config.json, Cursor MCP settings, or Windsurf config:
Option B: npx (no Docker required)
Option C: Direct API
The Discovery API is publicly accessible — no authentication required:
Why This Matters
The Discovery Gap in x402
The x402 protocol solves payment. It does not solve discovery. When hundreds of services exist but agents can't find, evaluate, or route to them intelligently, the protocol's full value is unrealized.
This project fills that gap with three layers:
- Discovery — Find x402 services by capability, category, price ceiling
- Quality signals — Uptime %, latency (ms), facilitator compatibility, ERC-8004 trust score
- Execution — scout_relay discovers, pays, retries, and returns results autonomously
What Makes This Different from x402.org/ecosystem
Live Catalog Stats
Catalog Sample
Example: Agent Workflow
Discovery only
Full autonomous execution via scout_relay
Payments use EIP-712 signed TransferWithAuthorization via the x402 HTTP protocol — not direct ERC-20 transfer. Signature verified server-side; on-chain settlement via receiveWithAuthorization.
CDP Builder Grant Context
This project is a direct implementation of two items from Coinbase's own public roadmap:
From PROJECT-IDEAS.md in coinbase/x402:
"Dynamic Endpoint Shopper — An agent that discovers an MCP registry, pays for access, chains results from multiple services"
From the CDP x402 facilitator roadmap:
"A discovery layer for buyers (human and agents) to find available services (Bazaar)"
We built the community Bazaar. It's live. It has quality signals the official page doesn't. And it uses x402 payments itself — x402_discover costs $0.010 USDC, paid via the protocol it serves. scout_relay extends this: it routes and executes x402 payments autonomously, charging its own x402 fee for the service.
What We've Shipped (11 days)
Architecture
Related Projects
Register Your Service
If you're building an x402-enabled service, add it to the catalog:
Or use the x402_register MCP tool from inside Claude/Cursor/Windsurf.
Want routing priority? Register a placement bid at POST https://x402-scout-relay.onrender.com/placement/bid (x402-gated, $0.01 registration fee). Your service gets weighted as a tiebreaker after trust-score filtering — merit first, always.
License
MIT
Built on Coinbase x402 protocol | Base Network | ERC-8004 | Model Context Protocol
Source: README.md at commit 4b8e69d
Tools
0Version history
1- v1.2.3LatestSep 16, 2026
Score
85% 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
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
