LION Keyless X402 Data + RPC For Agents
Attach keyless onchain enrichment and RPC-style data to agents that pay per call via x402 (TIGER payTo, CDP-ready GORILLA stack).
Overview
dev.workers.lionmaster-operations.lion-x402/lion-x402 is a MCP server for the Build phase that provides keyless x402-paid onchain enrichment and data for agents (GORILLA: TIGER+LION).
What is this MCP server?
- GORILLA stack combines TIGER + LION for keyless enrichment and onchain data
- x402 payment flow with TIGER payTo for per-request agent commerce
- Advertised as CDP-ready for Coinbase Developer Platform style workflows
- Hosted streamable-http MCP on Cloudflare Workers
- Targets agents that need paid data access without manual API key juggling
- Server version 1.7.0
- Remote transport: streamable-http
- Endpoint host: lion-x402.lionmaster-operations.workers.dev/api/mcp
What problem does it solve?
Your agent needs trustworthy onchain enrichment but you do not want to manage API keys and billing separately for every data provider.
Who is it for?
Advanced solo builders shipping agentic crypto tools, x402 experiments, or CDP-aligned automations that need remote enrichment.
Skip if: Beginners building non-crypto SaaS or teams that cannot use onchain payments and wallet infrastructure.
What do I get? / Deliverables
After you configure the remote MCP endpoint and x402 payment path, the agent can request enrichment and onchain data with pay-per-use semantics via TIGER payTo.
- Remote MCP access to LION keyless enrichment and onchain data
- x402 pay-per-request integration path for agents
- CDP-oriented hook for agent workflows citing GORILLA (TIGER+LION)
Recommended MCP Servers
Journey fit
Onchain agent tooling is implemented during Build when you wire payments and data feeds into your agent product. LION sits in integrations because it is a remote MCP facade for enrichment and chain data, not your app’s core UI or deploy pipeline.
How it compares
x402-paid onchain data MCP, not a traditional REST API key bundle or a wallet UI skill.
Common Questions / FAQ
Who is dev.workers.lionmaster-operations.lion-x402/lion-x402 for?
Experienced indie builders building agents that consume onchain data and pay via x402, especially when integrating with TIGER payTo and CDP-style flows.
When should I use dev.workers.lionmaster-operations.lion-x402/lion-x402?
Use it during Build when you are integrating paid, keyless enrichment and RPC-like onchain reads into an agent product.
How do I add dev.workers.lionmaster-operations.lion-x402/lion-x402 to my agent?
Add the streamable-http remote https://lion-x402.lionmaster-operations.workers.dev/api/mcp in your MCP client and complete x402/TIGER payTo wallet setup per LION documentation.