Skip to main content
Glama

Search x402 services

x402_search_services
Read-only

Find x402 payment services matching your criteria by searching a directory of 500+ listed services. Filter by query, category, network, status, and signability, then sort results to identify candidates.

Instructions

Your first call when you do not know which x402 service exists for a job: it narrows a directory of 500+ listed services to candidates. Filter by free-text query, category, network, live status, and whether the last observed 402 envelope is signable by a standard x402 client; sort by newest, uptime, cheapest, or endpoints. Returns up to 100 compact summaries a page: price in decimal USD, uptime, status, verification. Then x402_get_service for the full record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree-text search across name, description, category, base_url.
pageNo1-based page index into the filtered result set (see meta.total_pages).
sortNoServer-side sort order.newest
fieldsNoResponse detail: 'compact' (default) = lean summaries (identity, price, status, uptime, verification, networks, compliance grade), 'full' = every field including the per-service assessment block. Compact keeps a directory sweep small enough to not truncate.compact
statusNoFilter by live monitoring status.all
networkNoNetwork name or abbreviation, e.g. 'Base' or 'BSE'; any network code returned by /api/v1/networks is accepted. Omit for all.
categoryNoExact category name (see categories context). Omit for all.
per_pageNoServices per page, 1 to 100 (default 25). Higher values return larger results; with fields='full' a large page can be very heavy, so prefer compact when raising it.
signableNoFilter on the signability of the last observed 402 envelope: true = no EVM route of the service was observed missing the EIP-712 domain parameters (extra.name and extra.version) that a standard x402 client requires in order to sign a payment, false = at least one such route was observed. It describes the payment envelope on the wire, not the merit of the service. A service whose latest assessment has not measured that check yet matches NEITHER value, so omit this parameter to include it. Filtered server-side, so the result total covers the whole filtered set.
verified_onlyNoIf true, return only verified services. Filtered server-side, so the result total covers the whole verified set, not just this page.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv0.5.1

TDQS

A5/5.0
Behavior5/5

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

The description transparently explains the signable filter's nuanced behavior (neither true nor false if not measured) and the server-side filtering effects on result totals. Combined with readOnlyHint=true and openWorldHint=true annotations, the read-only nature and external dependency on network data are clear.

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 a single, well-structured paragraph that front-loads the purpose and then lists capabilities. Every sentence earns its place—there is no redundant or vague phrasing. It is concise yet comprehensive for a tool with 10 parameters.

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

Completeness5/5

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

Since no output schema is provided, the description adequately covers the return format (up to 100 compact summaries per page with price, uptime, status, verification). It also references external context (network codes, categories) and notes the pagination, making it complete for the intended search use case.

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

Parameters5/5

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

All 10 parameters are described in the schema, and the description adds significant value beyond basic definitions: it clarifies the signable filter's EIP-712 domain parameter check, explains the trade-off of per_page with fields='full', and details the difference between compact and full responses. This goes well beyond the schema's one-liners.

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's purpose: 'Your first call when you do not know which x402 service exists for a job.' It specifies the action (search) and the scope (directory of 500+ services), and mentions the follow-up sibling tool x402_get_service for full records, making the role unambiguous.

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

Usage Guidelines5/5

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

It explicitly says to use this as the first call when unknown, and directs to x402_get_service after narrowing candidates. It also explains the optional filters and their effects (e.g., signable filter semantics), providing clear guidance on when and how to apply them.

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

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/mcccsm/x402-list-mcp'

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