Menu

One-time licenses instead of per-call fees: shipping a paid MCP server with x402
📰

One-time licenses instead of per-call fees: shipping a paid MCP server with x402

DEV Community: opensource·Petra·about 19 hours ago
#25jlAdd9
#devtoopensource#devto#dev#license#payment
Reading 0:00
15s threshold

Everyone writing about paid MCP servers right now is charging per call. It makes sense: the x402 handshake inside tools/call is the obvious pattern, and the exact setup is well documented by now.

I went the other way: a one-time license, no per-call fees. This post is what I learned building and selling an MCP server that way.

What the tool does

Cierre de turno reads your public GitHub activity and writes one sentence that closes your workday: what you finished, what is still open, why it is stuck, and where to start tomorrow. The web version is free. The MCP version, which works from Cursor, Claude Code, OpenCode, or any MCP client, is a one-time 5 USDC payment on Base mainnet.

It is a tool people would use two or three times a day. That is exactly why per-call billing felt wrong: at that cadence, micropayments become a subscription with extra steps.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.