x402-agent-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BASE_RPC_URL | No | Base RPC URL. | https://mainnet.base.org |
| SOLANA_RPC_URL | No | Solana RPC URL. Defaults to mainnet if not set. | |
| EVM_PRIVATE_KEY | No | EVM private key (hex) for signing payments on Base. | |
| MAX_DAILY_SPEND | No | Maximum daily spend in USDC. | 10.00 |
| BASE_PRIVATE_KEY | No | Alias for EVM_PRIVATE_KEY. EVM private key (hex) for signing payments on Base. | |
| SOLANA_PRIVATE_KEY | No | Solana private key (base58) for signing payments on Solana. | |
| MAX_PAYMENT_PER_CALL | No | Maximum payment per call in USDC. | 0.50 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| x402_searchA | Search for x402 endpoints by keyword, category, or chain. Returns matching services with descriptions, prices, and URLs. |
| x402_list_categoriesA | List all available x402 endpoint categories with counts. |
| x402_describeB | Get detailed information about a specific x402 endpoint, including all available paths, methods, prices, and well-known discovery files. |
| x402_discover_urlA | Discover any x402 service by URL. Fetches /.well-known/x402 (payment details), /.well-known/ai-catalog.json (capabilities), and /llms.txt (agent summary). Returns a unified discovery object with chains, wallet, endpoints, and prices. |
| x402_healthA | Check if an x402 service is live and responding with 402 Payment Required. Verifies the service is operational before an agent pays for it. |
| x402_discover_urlsA | Batch discover multiple x402 services in parallel. Provide a list of URLs, each is probed for /.well-known/x402 and ai-catalog.json. Returns a summary array. |
| x402_crawl_directoryA | Crawl x402scan.com resources page to discover new x402 endpoints. Extracts service URLs, probes each for x402 support, and auto-adds confirmed services to the local directory. Returns summary of newly discovered services. |
| x402_fetchA | Fetch any x402-paid endpoint — handles 402 payment challenge automatically on Base, Solana or Casper. The agent never sees wallets or payment details. Just provide a URL and optional body. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly defined role covering category listing, searching, describing, discovering, health-checking, and fetching. The main overlap is between discover_url and discover_urls, which are the same operation in single and batch form, but this is a reasonable convenience rather than a true ambiguity.
All tools share the x402_ prefix and most use a verb or verb_noun pattern (list_categories, search, describe, discover_url, crawl_directory, fetch). The exceptions are health, which is a noun, and two discover verbs with slightly different forms, but the overall convention remains predictable.
Eight tools is well within the ideal range for this domain. Each tool addresses a distinct stage of discovering, evaluating, and consuming x402 services without excessive redundancy or missing core functions.
The toolset covers the full lifecycle from discovery (search, crawl, list categories), to verification (health, describe, discover_url), to interaction (fetch with automatic payment handling). No obvious dead ends or missing capabilities are apparent for an agent needing to work with x402 endpoints.