I monetized my MCP server on MCPize: tier structure, Stripe Connect, real numbers

I listed cipher-x402-mcp on MCPize this morning. MCP servers are turning into the API-for-agents layer the way npm packages were the API-for-humans layer ten years ago, and MCPize is the first marketplace that pays creators directly through Stripe Connect with an 85/15 split. This is the playbook I followed, with the actual numbers.

The product

cipher-x402-mcp is a small TypeScript MCP server. 8 tools, 7 of them x402-paid on Base mainnet USDC, one free for the wallet-audit ruleset. Prices range from $0.005 per breach check up to $0.25 per premium playbook chapter. The server is a stateless forward-only relay: it never custodies caller funds, it just surfaces the upstream 402 response and forwards the signed X-PAYMENT header.

Free GitHub source: github.com/cryptomotifs/cipher-x402-mcp. MCPize listing: live as of this morning, search "cipher" in their directory.

Why MCPize over the alternatives

I looked at four directories before picking.

• Smithery: large catalogue, free to list, no monetization layer. Good for discovery. Useless if you want to charge.
• mcp.so: community-curated index. Pure SEO play. No billing, no auth.
• Pulse.mcp.so: newer index, similar shape, no billing.
• MCPize: Stripe Connect built in, 85/15 creator split, supports Canadian Stripe accounts (which knocks out roughly 30% of "creator-friendly" platforms for me).

The MCPize 15% take is in the same range as Stripe's own 2.9% + Apple's 30% + Upwork's 10%. For a marketplace that handles OAuth, billing, dunning, refunds, and a public landing page, 15% is reasonable. The verified comparables are real: one creator (AWS Security Auditor MCP at $149/mo) is reportedly at 82 paid subs, roughly $8,500/mo at the 85% net. Another at $29/mo claims about $4,200/mo.

Tier design

I structured 4 tiers. These are the prices I shipped with, not what I'd ship with on day 30.

• Free: $0/mo, 100 requests/mo. Hits the wallet-audit free tool plus rate-limited paid ones. Conversion bait.
• Starter: $9/mo, 1,000 requests/mo. Single dev or hobby agent.
• Pro: $29/mo, 5,000 requests/mo. The price comparable cases cluster around. Real solo-dev tier.
• Team: $99/mo, 25,000 requests/mo. Multi-agent shops or one heavy automation.

Overage is $0.005 per request above the cap on Starter and Pro. The cap math came from a comparable scrape: AWS Security Auditor at $149 caps at ~10k req, which works out to $0.015/call effective. I priced 3x cheaper at the same effective floor because cipher-x402-mcp does less per call than a security auditor.

Honest disclosure: I have zero subscribers at publish time. These prices are derived from comparables, not validated by demand. The whole post is a 7-day experiment.

Setup time and friction

The mechanical setup, after the MCPize account already existed:

1. Onboarding wizard: 4 steps, ~4 min. Ask for display name, description, server endpoint URL, and tags.
2. Stripe Connect OAuth: 12 min. New Canadian Stripe account, business profile, banking info. The longest step.
3. Listing description, price tiers, rate limits: 18 min. Most of this was deciding tier names, not typing.
4. Cover image upload: blocked at "89% complete, upload logo". I had a brand kit repo from last sprint, dropped a 1024×1024 PNG, gate cleared in 30 seconds.
5. Publish click: 1 second.

End-to-end: 90 minutes. Could have been 60 if the brand kit was already in the right format.

What I'd do differently

Three things, in order of how much they probably matter.

• Tier names are flat. "Free / Starter / Pro / Team" is the default and reads as default. "Hobby / Indie / Studio / Fleet" would test better for the agent-buyer audience.
• Pricing is too compressed at the top. $99 Team is fine for solo shops, but real automation buyers will pay $299 for unlimited. I left money on the table to avoid scaring early subs.
• Cover image is a flat logo on a dark background. It needs more visual hierarchy: 1 product name + 1 capability line + the x402 badge. Will A/B in week 2.

Close

Listing: mcpize.com (search "cipher"). Free repo with the full MIT source: github.com/cryptomotifs/cipher-x402-mcp. To list your own MCP server, the wizard takes about 90 minutes if your Stripe account exists. If you ship one, post the URL and I'll cross-check the tier math against my comparables.

Tagged: #mcp #ai #claude #monetization #indiedev