x402-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAX_PAY_USD | No | Maximum payment amount in USD per call. | 1 |
| THREE_WS_BASE | No | Base URL for three.ws API. | https://three.ws |
| SOLANA_RPC_URL | No | Solana mainnet RPC endpoint URL. | https://api.mainnet-beta.solana.com |
| REQUIRE_CONFIRM | No | If 'true', requires explicit confirm=true parameter in pay_and_call. | true |
| SOLANA_SECRET_KEY | No | Base58 secret key of the Solana wallet that holds USDC. Required for pay_and_call and x402_wallet (to see balance) but not for read-only tools. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| x402_walletA | Show a Solana wallet's address and live SOL + USDC balance. With no |
| find_servicesA | Search the live x402 facilitator network (PayAI + Coinbase CDP bazaar) for paid services — HTTP APIs and MCP tools. Returns each match with its price, networks, and resource URL. Pass a resource into pay_and_call to use it. Read-only. |
| inspect_endpointA | Fetch an x402 endpoint and return its 402 payment requirements — every accepted scheme, network, asset, price and pay-to address — WITHOUT paying. If the endpoint is free, returns its result instead. No signer required. Use this to learn the cost before pay_and_call. |
| pay_and_callA | Call a paid x402 endpoint and settle the payment automatically, then return the result. Two modes:
• Self-custodial (default): signs with SOLANA_SECRET_KEY or Pay in USDC (default) or, when the endpoint advertises it, in $THREE (set token:"three"). Bounded by max_usd and the MAX_PAY_USD cap; refuses before any money moves if the price is over the cap. With REQUIRE_CONFIRM on, the call refuses until re-issued with confirm:true. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/nirholas/x402-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server