Monetize Your MCP Server: Per-Call Pricing and Payouts

To monetize an MCP server you have to decide what the buyer is paying for: access, usage, or outcomes. In practice that comes down to three models. Getting listed so people can find your server is a separate step — see how to publish an MCP server to the marketplace, which is free.

For tools called by agents, per call wins most of the time. An agent may call a lookup three times in one conversation and three hundred times in a batch job an hour later; a flat subscription either overcharges the first buyer or loses money on the second. Credits are per-call pricing with a unit that lets one balance cover tools of different weight.

Price in two passes. The cost floor is what one call costs you to serve: upstream API fees, compute, the data licence, a share of support. Never sell below it. The value anchor is what the answer is worth to the buyer: the minutes of manual research it replaces, the bounce it prevents, the bad lead it filters. The price lives between the two, closer to the floor for commodity lookups and closer to value for answers nobody else can give.

• Charge for answers, not attempts. A lookup that finds nothing should be free or refunded; buyers compare vendors on cost per useful result.
• Keep the unit legible. “5 credits per company found” is easy to budget; “0.4 credits per token of output” is not.
• Price heavy tools separately. A tool that scans a whole site should not cost the same as a key-value lookup, or light users subsidise heavy ones.
• Publish the price on the tool itself, in its description. An agent choosing between tools can only weigh cost it can read.

On the Hub you set a price of 1 to 1,000 credits per call for each tool you offer. Buyers pay for credits on our graduated scale ($2.00 per 1,000 up to 100,000, $1.20 per 1,000 up to 1,000,000, $0.80 per 1,000 above 1,000,000). You earn a fixed seller rate of $0.80 per 1,000 billable credits your tools use, and keep 80% of it after our 20% platform fee — $0.64 per 1,000 credits. The seller rate is pegged to the lowest volume tier on purpose, so a large buyer’s volume discount never reduces what you are owed.

Two things worth knowing before you set a price. Marketplace tools require billing on the buyer’s side — free monthly credits cover first-party tools only — so every call to your tool is a paid call. And refunds are automatic: if your server errors, times out or returns output that fails our scan, the buyer is refunded and that call earns nothing.

A buyer wiring your tool into an agent is trusting you with their agent’s context and their money. The checks we run before a server goes live are a good list of what any buyer should expect, wherever you sell:

Beyond the checklist, buyers want documentation they can act on (what each tool returns, when it charges, how it fails), stability (a definition that changes without notice is indistinguishable from an attack — see MCP server monitoring), and predictable errors rather than empty results that read as data.

Once live, a health check keeps what is sold honest. Every server is probed regularly:

• 3 consecutive failed probes suspend the server until it answers again.
• A tool whose definition changes upstream is suspended — the tool, not the server — and a tool that appears upstream is never offered automatically. Resubmit to change what you sell.
• An error rate of 20% or more over at least 20 calls in an hour suspends the server.
• Domain proofs older than 30 days are re-checked; a proof that no longer holds suspends the servers relying on it.

Every result your tool returns is also screened on the way out, and a blocked result is withheld and refunded. The full terms are on the Hub terms page.

Sellers are paid through Stripe Connect and complete Stripe’s own onboarding; we are the merchant of record, so buyers pay us on one invoice and you never chase a customer. An earning settles when the buyer’s invoice is paid, becomes payable 14 days later, and is paid on the 15th of the month once your balance reaches $25. If a buyer is refunded, the matching share of your earnings is deducted; if a buyer disputes a charge, the related unpaid earnings are held, and a lost dispute is deducted from future earnings.

If your data already lives in a database, an API or a docs repository, you can also publish read-only tools over it without running a server at all, reviewed and paid out the same way. Both start in the developer portal — create an account and open Sell.