obolpay-x402-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discover | Return the x402 gateway's machine-readable manifest: price, token, network, recipient, payment flow, free-preview and proof-of-purchase capabilities. No payment required. |
| preview | Fetch the HTTP 402 challenge and return its FREE preview (a sample of the paid dataset) plus the price/invoice, so the agent can decide whether to pay. No payment required. |
| purchase | Pay the quoted USDC on Base and return the unlocked {data, receipt}. Requires env X402_AGENT_PRIVATE_KEY (a Base wallet with >= the quoted USDC + gas). WARNING: this spends real USDC on-chain. |
| verify_receipt | Verify a proof-of-purchase receipt with the gateway (recovers the EIP-191 signer and checks it equals the server's receipt signer). Anyone can call this — no payment required. |
| balance | Check a prepaid balance: remaining balance, calls_remaining, and next_nonce. Pass an address, or leave blank to use the wallet from X402_AGENT_PRIVATE_KEY. |
| topupA | Credit a prepaid balance from an on-chain USDC deposit to the recipient. First send USDC to the recipient on Base, then call this with the tx_hash. |
| spend_gasless | Fetch the paid data by drawing from the prepaid balance — GASLESS, NO on-chain tx. This is the habitual-use path: after one topup you can call this many times for free (only gas-free balance debit). Requires X402_AGENT_PRIVATE_KEY with a funded balance. |
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
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- 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/Hiroshi-Ichiyanagi/obolpay-x402-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server