What is the key difference between X402 Discovery MCP and X402search MCP?

X402 Discovery MCP belongs to the Aggregators category with local stdio execution, while X402search MCP belongs to the Aggregators category with local stdio execution.

How do I install X402 Discovery MCP or X402search MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are X402 Discovery MCP and X402search MCP free or paid?

X402 Discovery MCP operates under a Freemium model (API Key required). X402search MCP operates under a Paid Service model (other).

Which MCP server has more tools and community activity?

X402 Discovery MCP lists 9 tools with 2 views and 4 GitHub stars. X402search MCP lists 6 tools with 2 views and 2 GitHub stars.

Can I use both X402 Discovery MCP and X402search MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

X402 Discovery MCP vs X402search MCP

In-depth architectural comparison of the X402 Discovery MCP and X402search MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

X402 Discovery MCP

Aggregators · Local stdio

Quality: 53/100 (Good) | Auth: API Key required

X402search MCP

Aggregators · Local stdio

Quality: 48/100 (Fair) | Auth: other

Verdict Summary: Choose X402 Discovery MCP if you need specialized Aggregators tools running via a local process. Choose X402search MCP if your workspace requires Aggregators integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose X402 Discovery MCP when:

You need dedicated capabilities in the Aggregators domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: X402_PAYMENT_HEADER, X402_WALLET_ADDRESS, X402_API_URL.
Primary tools included: x402_discover, x402_health, x402_register.

Explore X402 Discovery MCP Details

Choose X402search MCP when:

You need dedicated capabilities in the Aggregators domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Paid Service).
You have access to required keys: EVM_PRIVATE_KEY.
Primary tools included: Keyword search across 14,000+ x402-enabled APIs, Network filtering, Maximum-price filtering in USDC.

Feature & Specification Comparison

Specification	X402 Discovery MCP rplryan Aggregators	X402search MCP x402-index Aggregators
Summary	Runtime discovery layer for x402-payable APIs. Agents discover and route to pay-per-call x402 endpoints by capability, get quality-ranked results with trust scores (0-100), and pay per query via x402. Includes MCP server, Python SDK, and CLI (npm install -g x402scout).	Search 14,000+ x402-enabled HTTP APIs by keyword. Agents pay $0.01 USDC per search via x402 micropayments on Base mainnet — no API keys required. Larger index than any other x402 discovery layer.
Category & Scope

Tools & Capabilities Breakdown

X402 Discovery MCP Tools (9)

x402_discover

Semantic search across the live catalog by keyword, category, max price

x402_health

Real-time uptime + latency check for any registered service

x402_register

x402_attest

ERC-8004 trust score and reputation signals for a service

x402_scan

Full x402 compliance scan: live config, trust score, mismatch detection

scout_route

Discover best service for an intent + execute x402 payment

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

X402 Discovery MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "rplryan-x402-discovery-mcp": {
      "command": "npx",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/rplryan/x402-discovery-mcp:latest"
      ],
      "env": {
        "X402_PAYMENT_HEADER": "YOUR_X402_PAYMENT_HEADER_HERE",
        "X402_WALLET_ADDRESS": "YOUR_X402_WALLET_ADDRESS_HERE",
        "X402_API_URL": "YOUR_X402_API_URL_HERE"
      }
    }
  }
}

X402search MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "x402-index-x402search-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "x402search-mcp@1.0.3"
      ],
      "env": {
        "EVM_PRIVATE_KEY": "YOUR_EVM_PRIVATE_KEY_HERE"
      }
    }
  }
}

Frequently Asked Questions

X402 Discovery MCP is categorized under Aggregators and uses a local stdio subprocess. In contrast, X402search MCP belongs to Aggregators using local stdio subprocess. Select X402 Discovery MCP when you need capabilities focused on aggregators and X402search MCP when you require tools for aggregators.

More alternatives to X402 Discovery MCP More alternatives to X402search MCP Aggregators category hub