Skip to main content
Glama
x402-index

x402search

by x402-index
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

x402search MCP Server

Search 14,000+ x402-enabled HTTP APIs from any MCP-compatible agent.

Version: 1.0.3 · License: MIT · Cost: $0.01 USDC per search · Base mainnet · No account needed

npm: https://www.npmjs.com/package/x402search-mcp
PyPI: https://pypi.org/project/x402search-mcp
API: https://x402search.xyz

Requirements

Related MCP server: 2s

Install: Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "x402search": {
      "command": "npx",
      "args": ["x402search-mcp@1.0.3"],
      "env": {
        "EVM_PRIVATE_KEY": "0xYOUR_PRIVATE_KEY_HERE"
      }
    }
  }
}

Config file location:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Install: Claude Code

claude mcp add x402search -- npx x402search-mcp@1.0.3

Then set your key:

export EVM_PRIVATE_KEY=0xYOUR_PRIVATE_KEY_HERE

Install: Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "x402search": {
      "command": "npx",
      "args": ["x402search-mcp@1.0.3"],
      "env": {
        "EVM_PRIVATE_KEY": "0xYOUR_PRIVATE_KEY_HERE"
      }
    }
  }
}

Install: Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "x402search": {
      "command": "npx",
      "args": ["x402search-mcp@1.0.3"],
      "env": {
        "EVM_PRIVATE_KEY": "0xYOUR_PRIVATE_KEY_HERE"
      }
    }
  }
}

Install: Python agents (LangChain, CrewAI, AutoGen, GAME SDK)

pip install x402search-mcp
from x402search import search_x402_apis
results = search_x402_apis(
    query="token price API ethereum",
    private_key="0xYOUR_PRIVATE_KEY_HERE"
)
print(results)

Full docs: https://pypi.org/project/x402search-mcp

Quick Test

EVM_PRIVATE_KEY=0xYOUR_KEY npx x402search-mcp@1.0.3

Tool: search_x402_apis

Parameter

Type

Required

Description

query

string

yes

e.g. "token price API", "DEX swap routing"

network

string

no

e.g. "eip155:8453" for Base mainnet

max_price_usdc

number

no

Filter to APIs at or below this price

limit

number

no

Max results (default 10, max 50)

Virtuals ACP Integration

x402search is available as a native ACP agent on the Virtuals protocol marketplace.

  • Agent ID: 22531

  • Agent profile: https://app.virtuals.io/acp/agent-details/22531

  • Job name: x402search

  • Price: 0.01 USDC per search

  • Accepts crypto, DeFi, and blockchain API discovery queries

  • Rejects off-topic requests automatically at the request phase

  • Returns structured results: endpoint URLs, payment metadata, network, and relevance rank

Links

Available Tools

1 tool
search_x402_apisA

Search 13,000+ x402-enabled HTTP APIs by capability, category, network, or keyword. Returns ranked results with endpoint URLs, pricing, and payment metadata. Use this to discover paid APIs for any capability your agent needs. Costs $0.01 USDC per search on Base mainnet.

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesNatural language search query, e.g. 'weather data', 'image generation', 'crypto prices', 'web scraping'
networkNoFilter by CAIP-2 network identifier, e.g. 'eip155:8453' for Base mainnet
max_price_usdcNoFilter results to APIs priced at or below this amount in USDC, e.g. 0.01
limitNoMax results to return (default 10, max 50)

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behavioral traits: the tool performs searches (not mutations), costs $0.01 USDC per search on Base mainnet, and returns ranked results with specific metadata. It could improve by mentioning response format or error handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is efficiently structured in three sentences: the first explains what the tool does, the second provides usage guidance, and the third discloses cost information. Every sentence adds value with zero waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and 100% schema coverage, the description is mostly complete. It covers purpose, usage, cost, and result format well, but could benefit from mentioning response structure or error cases to be fully comprehensive for a search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all four parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema, maintaining the baseline score of 3 for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches through 13,000+ x402-enabled HTTP APIs using specific criteria (capability, category, network, keyword) and returns ranked results with endpoint URLs, pricing, and payment metadata. It specifies the verb 'search' and resource 'x402-enabled HTTP APIs' with no siblings to differentiate from.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use this tool: 'to discover paid APIs for any capability your agent needs.' It does not mention when not to use it or name specific alternatives, but with no sibling tools, this guidance is sufficient for the given context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.3
    • First observedsearch_x402_apis
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool has a single, clearly defined purpose: searching x402-enabled APIs. Agents cannot misselect between tools as there is only one option.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The tool name 'search_x402_apis' follows a clear verb_noun pattern, which would be consistent if more tools were added.

Tool Count2/5

One tool is too few for a server focused on API discovery, as it severely limits functionality. While the tool covers search, there are obvious gaps like filtering, sorting, or accessing detailed API information, making the server feel thin and incomplete for its domain.

Completeness2/5

The server is severely incomplete for API discovery. It only provides search functionality, missing essential operations such as retrieving detailed API metadata, filtering results, or managing saved searches. This will cause agent failures when trying to perform comprehensive API exploration tasks.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/x402-index/x402search-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server