Flipr X402
Wire a coding agent to an x402 paywall on Base so it can spend USDC to call a provably fair coin-flip API with streak-based pots.
Overview
io.github.iainkek/flipr-x402 is a Build-phase MCP remote that lets AI agents pay USDC on Base via x402 to access Chainlink VRF coin-flip gameplay with streak pots.
What is this MCP server?
- Streamable HTTP remote at flipr-x402.fly.dev/mcp—no local npm package required
- x402 gateway pattern: agents pay USDC on Base before invoking flip actions
- Chainlink VRF-backed coin flips with streak mechanics and pot wins
- Suited for experimenting with agent-native commerce and Base L2 spend
- Registry schema 2025-07-09; server version 0.1.0
- Remote MCP URL: https://flipr-x402.fly.dev/mcp (streamable-http)
- Server version: 0.1.0
- Settlement asset: USDC on Base; randomness: Chainlink VRF
What problem does it solve?
You want agents to call paid APIs without baking in traditional billing keys, but lack a working x402 + stablecoin example on a real L2.
Who is it for?
Indie builders prototyping agent wallets, x402 gates, or Base USDC flows who need a live MCP remote to pair with Claude Code or Cursor.
Skip if: Teams that need enterprise billing, fiat-only checkout, or production gambling compliance without their own legal review.
What do I get? / Deliverables
Your agent can register the Fly.dev MCP endpoint and exercise USDC micropayments against a VRF-backed flip service during integration testing or demos.
- Registered remote MCP endpoint in your agent
- Exercised paid flip/streak flows over x402
- Reference pattern for agent-native USDC tool access
Recommended MCP Servers
Journey fit
Payment-gated agent APIs are assembled during product build when you connect wallets, gateways, and MCP remotes—not during ideation alone. This is a remote MCP integration (streamable HTTP) that exposes a micropayment + on-chain randomness workflow to your agent stack.
How it compares
On-chain x402 payment gateway MCP, not a generic REST wrapper skill or local codegen plugin.
Common Questions / FAQ
Who is io.github.iainkek/flipr-x402 for?
Solo and indie developers shipping agent products who want a real x402 + USDC-on-Base integration they can hit from an MCP client.
When should I use io.github.iainkek/flipr-x402?
Use it while building agent integrations when you need to test paid tool calls, VRF-backed randomness, or streak-based game logic over MCP.
How do I add io.github.iainkek/flipr-x402 to my agent?
Add the streamable-http remote URL https://flipr-x402.fly.dev/mcp in your MCP server config (Claude Code, Cursor, or compatible hosts), fund USDC on Base for the agent wallet, then invoke the server tools from the client.