MCP‑BILLING · boilerplate spec validating demand — not yet built

Draft 01 — pre‑launch

Ship MCP servers with auth & billing already wired.

A self-hosted boilerplate for developers building Model Context Protocol servers: OAuth 2.1, per-call billing, rate limits and multi-tenancy pre-configured, deployed with wrangler deploy. You keep the code and 100% of revenue — no marketplace, no gateway cut.

§1

The problem

Building the MCP tool takes a weekend. Wiring identity and payments around it doesn't. This is a common story from builders shipping MCP servers in 2026:

$ adding OAuth to the MCP server... Four hours in, still reading RFC 9728. Debugging PKCE code challenges at 1am. Not one line of it made the server smarter — it was just identity plumbing. Shelved the auth work. Shipped with a static API key instead.

— paraphrased from builder reporting on MCP auth, 2026. Source ↗

§2

Why now

10,000+active public MCP servers as of March 2026 (Anthropic)
<5%of MCP servers are monetized — billing infra is still unbuilt
40%of exposed MCP services run with no auth at all (Censys)
§3

What's in the box

§4

Founding price

$79$149 at public launch

One-time. Locked in for the first 100 buyers if this validates. Nothing is charged today — this only confirms interest.

Would you pay for this?

Join the waitlist →