🧵 1/ Just dropped a 90-sec demo of MCPay.fun for the Coinbase hackathon project that turns x402 into MCP payments.

"Monetize your MCP server in one click"

Check this out @coinbasedev @buildonbase @pinatacloud

Farcaster and IPFS at Scale | https://docs.pinata.cloud/farcaster/farcaster-api

Mainly posting from @coinbase. 

https://www.coinbase.com/developer-platform

3/ Tool Stack

• x402 for the 402 ↔️ payment dance
• CDP Wallet to sign + send USDC on Base
• Pinata private IPFS MCP server so agents can pay-to-pin files

Amongst others...

All open-sourced here →

4/ Demo

See how I register something super quick and make micropayments via MCP for tool use

https://youtu.be/FEMqtCWR02s

3/ Tool Stack

• x402 for the 402 ↔️ payment dance
• CDP Wallet to sign + send USDC on Base
• Pinata private IPFS MCP server so agents can pay-to-pin files

Amongst others...

All open-sourced here → https://github.com/microchipgnu/mcpay.fun

2/ Why?

Developers struggle to monetize AI tools and APIs without setting up full SaaS infrastructure, managing API keys, or relying on centralized marketplaces.

Consumers and AI agents face friction: paywalls, subscriptions, OAuth flows, or unavailable APIs make it hard to access services on demand.

potentially TMI but would love to know what API key this leverages under the hood?

https://www.mcpay.fun/servers/9a198661-039a-4dae-9538-a356e3f83644#integration

weatherXM vs openweather vs other

feel like that might affect my purchasing decision

I see and that's good insight. I don't know for this one in particular, but would it be sufficient if it says in the description? 

I'm thinking of ways to increase the trust to MCP servers (with reliability checks, proofs that results are good, etc)