X402 Service Discovery

Name: X402 Service Discovery
Author: rplryan

@rplryan

About X402 Service Discovery

The missing discovery layer for x402. AI agents can pay for services autonomously via HTTP 402 — but first they need to find them. This MCP server provides 5 tools to discover, rank, and verify x402 payment-gated APIs by capability, price, ERC-8004 trust score, and facilitator co

#ai-agents-blockchain-search-integration-search-api-http-server

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "x402-discovery": {
      "type": "streamable-http",
      "url": "https://x402-discovery-api.onrender.com/mcp"
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is X402 Service Discovery?

X402 Service Discovery is an MCP server that connects AI agents (Claude, Cursor, Windsurf) to a continuously updated catalog of 251+ x402-payable services, providing real-time quality signals, facilitator-compatibility checks, and ERC-8004 trust scoring. It is built for agents needing to find, evaluate, and register x402 endpoints inside their workflow.

How to use X402 Service Discovery?

Configure the server in your claude_desktop_config.json, Cursor MCP settings, or Windsurf config using either Docker (docker run -i --rm ghcr.io/rplryan/x402-discovery-mcp:latest) or npx (npx -y @rplryan/x402-discovery-mcp). Once running, use the five MCP tools (x402_discover, x402_health_check, x402_register, x402_trust, x402_facilitator_check) from your AI agent.

Key features of X402 Service Discovery

Semantic search across 251+ services by keyword, category, price ceiling
Live health checks with uptime % and latency (ms) per service
ERC-8004 trust scoring and facilitator-compatibility flags
Free service registration and catalog submission
Auto-scan of catalog every 6 hours from multiple ecosystems

Use cases of X402 Service Discovery

An agent searching for blockchain analytics services under $0.01 USDC
Verifying a service’s facilitator compatibility before committing to a payment
Registering a new x402-payable endpoint into the live catalog
Checking real-time uptime and latency of a service before calling it

FAQ from X402 Service Discovery

How does this differ from the official x402.org catalog?

The official x402.org catalog lists names and URLs only. X402 Service Discovery adds uptime monitoring, latency data, facilitator-compatibility flags, ERC-8004 trust signals, agent-native usage prompts, and semantic search — all auto-updated every 6 hours.

What are the runtime requirements?

You need either Docker installed (recommended) or Node.js to run via npx. The MCP server connects over stdio; the backend API is hosted publicly on Render and requires no local setup.

Is there a cost to use this MCP server?

Only the x402_discover tool costs $0.005 USDC, paid via the x402 protocol (the server eats its own dogfood). All other tools (x402_health_check, x402_register, x402_trust, x402_facilitator_check) are free.

Does the server require authentication?

No. The Discovery API is publicly accessible — no API keys or authentication are needed for the MCP server or its tools. Payment for x402_discover uses EIP-712 signed transfers per the x402 protocol.

How often is the service catalog updated?

The catalog auto-scans every 6 hours from x402.org/ecosystem, awesome-x402, and x402scan.com. It indexes more than 251 services across data, compute, agent, and utility categories.