MCP CREATOR ECONOMY

Sell MCP Servers: Every 2026 Marketplace Compared

You built an MCP server. Now the awkward part: the biggest directories in the ecosystem pay $0 — Smithery charges creators for hosting instead. Here is where server creators actually earn in 2026: hosted marketplaces with 70–85% revenue shares, the x402 pay-per-call rails agents can pay without a human, the five ways listings earn nothing, and the realistic earnings math nobody's landing page prints.

See MCP tools in a real harness Compare creator payout terms

The $0-directory problem

The MCP ecosystem's default distribution is free. PulseMCP tracks 20,274 servers; of 12,000+ public servers counted in March 2026, fewer than 5% have monetized successfully. That is not because developers didn't try — it is because the most popular places to list a server are catalogs, and catalogs have no payment rails:

Platform	Type	Creator economics	What it really is
Smithery	Directory + hosting	$0 revenue — creators pay ~$30/mo for hosting tiers	Catalog with paid hosting; no payment rails
Glama	Directory + hosting	$0 revenue — platform keeps subscription income	Catalog; ~$26/mo subscription model
mcp.so / PulseMCP	Directory only	$0 — no sales path at all	Discovery, stars, reputation
MCPize	Marketplace + hosting	80% revenue share (85% Founding Member rate before Jun 10 2026), monthly Stripe payouts, $25 minimum	Subscriptions + x402 pay-per-call in USDC
Apify Store	Marketplace + hosting	Direct creator billing, reported 15–20% platform cut	Strongest for devs already on Apify
AgentStack	Marketplace	70/30 split via Stripe Connect; reports $102.3K paid to creators	MCP servers + skills + toolkits, security-reviewed per version
FiatDock	Payment rail (non-custodial)	0% first month, then 1% — settles per call straight to your wallet	x402 pay-per-call; optional $20/mo Verified badge
VibeFuse marketplace	Marketplace in a harness	80% flat via Stripe Connect, $0.50–$500 creator-set pricing, no listing fee	Widgets, skills, styling packs — canvas-demonstrable assets

Read the first three rows together: distribution without payment. Listing in a directory earns reputation and installs — worth doing, because reputation feeds sales — but every dollar earned through an MCP server in 2026 flows through one of the paid routes below.

x402: the rail where agents pay without a human

Every monetization model except one has the same flaw for MCP: it assumes a person is present. A subscription needs someone to enter a card. Prepaid credits need someone to top up and notice when the balance runs out. Invoicing needs a purchase order. An autonomous agent has no person on hand at 3am — which is exactly when agents run.

Model	How it works	Best for
Pay-per-call (x402)	First call returns HTTP 402 with the price; agent signs a USDC authorization and retries; payment settles on-chain to your wallet	Autonomous agents, data/lookup/compute tools — the only model a machine completes alone
Subscription	Recurring fee, enforced by API key, usage quotas and overages managed by the marketplace gateway	Human SaaS buyers; predictable MRR
Prepaid credits	Buyer tops up a balance; calls draw it down	Bursty use — but you hold someone else's money
API key + invoicing	Issue keys, bill in arrears	Enterprise procurement — slowest to get paid
Sponsorship / ads	A third party pays for placement in your output	Consumer scale — and your output stops being neutral

The x402 mechanics, concretely: an unpaid call returns HTTP 402 with the payment requirements base64-encoded in the PAYMENT-REQUIRED header (network, USDC asset, atomic amount, recipient). The agent signs an EIP-3009 transferWithAuthorization and retries; a facilitator relays it and pays the gas, so the paying agent needs no ETH. Payment settles to your Base wallet at call time — non-custodial, no payout schedule. Across the ecosystem in a recent 30-day window: $1.11M settled over 3.69M transactions, with observed call prices clustering at $0.002–$0.03. The floor is $0.001 per call, and below it rounding can make a 1% commission exceed 50% of the call — platforms refuse those listings rather than overcharge you quietly.

One structural catch FiatDock's own docs print plainly: a stdio/npm package listing runs on the buyer's machine — no call passes through any meter, so it can never collect. If you want per-call revenue, your server needs a hosted HTTPS endpoint; ~75% of tracked MCP servers are stdio-only, which means three quarters of the ecosystem is structurally unable to take a per-call payment today.

Five ways an MCP listing earns nothing

Documented failure modes from the payment rails themselves — every one of them silent from the seller's side until you check the money:

1. The stdio trap

Your npm package runs on the buyer's machine. No meter, no 402, no revenue — no matter how many installs. Fix: host at a public HTTPS endpoint, then swap the package name for that endpoint.

2. No payout wallet

A paid listing with no wallet set answers 409 instead of a price while looking perfectly normal in the catalog. Fix: set the wallet — the listing becomes buyable immediately, no re-publish.

3. Ghost tools

Naming a tool your server does not expose in tools/list means buyers pay for errors. Fix: every priced tool must appear in the live tool list — rails probe this at publish time.

4. Sleeping hosting

Hosting that sleeps or a tunnel URL that moves turns your endpoint into a dead listing. Fix: persistent hosting; expect health probes every few hours.

5. Price in prose, zero in the field

Writing "$0.01 per call" in the description while the price field is 0 means agents call your server free, forever — agents read the field, not your copy. Fix: set priceUsd explicitly; never rely on defaults.

Realistic earnings: the winner pyramid

Every marketplace landing page shows the top earner. Here is the actual distribution across 12,000+ public MCP servers (March 2026), assembled from monetization research across the rails:

Tier	Monthly revenue	What it takes
Top 1%	$10K+ MRR	21st.dev hit $10K MRR in six weeks selling UI-component generation — a product devs already wanted, sold where they already are
Successful ~5%	$3K–$10K/mo	Clear niche + continuous improvement + actual support
Middle tier	$100–$500/mo	Pocket money; usually one good integration, thin distribution
Bottom 95%	$0	Free, abandoned, or hobby — listed in a directory with no payment rail

Verified individual datapoints: one developer moved an MCP server to Apify Store and went from a $500/month plateau elsewhere to $2,000/month on usage-based pricing — distribution and metering, not the code, changed. On x402, FiatDock's own first-party tools took $0.14 from two paying wallets in their launch window — the rails publish their own modest numbers, which is more honest than most. The GPT Store set the precedent agents-marketplace economics keep repeating: ~$0.03 per conversation means $1,000/month needs 33,000+ quality conversations, and the median creator earned $0. The B2B pattern is where the $100K+ solo devs cluster: template a lead-qualification agent at $1,500 setup + $300/month maintenance, replicate across clients.

Pricing guidance that survives contact with data: real x402 calls settle in the $0.002–$0.03 band, and the widest buyer base belongs to the cheapest services — price a lookup like a lookup. If your tool wraps a genuinely expensive model call or paid upstream API, price to cover it and expect fewer buyers rather than more revenue. MCPize's published formula (price = time saved × hourly rate × 10%) is a reasonable sanity check for subscription tiers: a server saving a developer two hours a month at a $100/hour valuation supports roughly $20/month.

Where VibeFuse fits

VibeFuse is the buyer-side of this economy: a free Windows harness where Settings → Tools hosts branded MCP cards (Google Workspace, Drive, GitHub, Copilot, Discord, Linear) plus custom stdio servers — every connected tool exposed to the built-in agents, no separate MCP host to babysit. That makes every VibeFuse install a potential buyer for whatever you sell.

The VibeFuse marketplace pays creators a flat 80% revenue share via Stripe Connect with creator-set pricing from $0.50 to $500 and no listing fee — today for widgets, skills, and styling packs, the assets buyers can watch run on the canvas before they pay (demonstrability is why visual products convert better in every mature digital marketplace). MCP servers are the tool layer of that same canvas economy: the first ever free widget-based AI harness, an open-source marketplace where creators make money selling what they build, local/offline processing, works in any app.

MCP tools in a real harness How to sell AI widgets (80% share)

✓ 80% flat creator payouts
✓ No listing fee, $0.50–$500 pricing
✓ Buyers install in one click
✓ Free harness for buyers

Sell where creators keep 80% See the payout terms

Explore VibeFuse & harness guides

Selling MCP servers FAQ

Can you sell an MCP server?

Yes — three paid routes exist as of 2026, and they behave very differently. Hosted marketplaces (MCPize, Apify Store) take a 15–20% cut and hand you 80–85% via monthly Stripe payouts. Payment rails like FiatDock run x402 pay-per-call: the agent itself pays per tool call, settling straight to your wallet, with the platform taking 0–1%. Direct B2B — invoicing an enterprise for a custom server — is where the biggest contracts live. What does not pay: the big directories (Smithery, Glama, mcp.so, PulseMCP) are catalogs, not payment rails. Smithery actually charges creators ~$30/month for hosting tiers while paying $0 in revenue share.

How much do MCP server creators earn?

Be suspicious of anyone promising a number without a distribution behind it. Of 12,000+ public MCP servers tracked as of March 2026, fewer than 5% have monetized successfully — and the winners follow a steep pyramid: top 1% at $10K+ MRR (21st.dev reached $10K MRR in six weeks with UI component generation), the successful 5% at $3–10K/month, a middle tier at $100–500/month, and the bottom 95% at $0. On x402 rails the whole ecosystem settled $1.11M across 3.69M transactions in a 30-day window, with top data-API sellers earning roughly $1–3K/month. MCPize markets "creators earning $400–2,000+/month" — a vendor claim, treat it as such. The honest median is $0; the honest upside is real but concentrated.

Which MCP marketplace pays the highest share?

Depends what you count. MCPize pays 80% of every sale (85% for servers that activated monetization before its June 10, 2026 Founding Member deadline), paid monthly via Stripe Connect. AgentStack pays 70% and reports $102.3K paid out to creators across 140,140 listings. FiatDock takes 0% for your first month, then 1%, but only on hosted per-call endpoints — it never holds your money at all. Apify Store pays direct creator billing with a reported 15–20% platform cut. The directories pay $0 regardless of how good your server is. VibeFuse pays a flat 80% on widgets, skills, and styling packs with no listing fee and creator-set pricing from $0.50 to $500.

Why does my MCP server earn nothing?

Five documented failure modes cause almost every $0 listing: (1) your listing is a stdio/npm package — it runs on the buyer's machine, so no call ever passes through a meter, and it can never collect per-call revenue; (2) you published a paid listing without setting a payout wallet, so agents get a 409 error instead of a price; (3) you named a tool your server does not actually expose in tools/list; (4) your hosting sleeps or your tunnel URL moves, so buyers hit dead endpoints; (5) you wrote the price in the description while the actual price field is 0 — agents read the field, not your prose. PulseMCP tracks 20,274 servers and only ~24% are remote-available: three quarters of the ecosystem is structurally unable to take a per-call payment.

What is x402 and how does pay-per-call work?

x402 is the HTTP 402 "Payment Required" flow adapted for agents: your server's first unauthenticated response returns a 402 with the price in a PAYMENT-REQUIRED header; the agent signs a USDC authorization (EIP-3009 transferWithAuthorization) and retries with it; a facilitator submits the payment and pays the gas. The agent needs no wallet UI, no signup, no API key — which matters because an autonomous agent has no person around at 3am to enter a card. That is the dividing line between monetization models: subscriptions, credits, and invoicing all need a human step; only per-call lets a machine complete the transaction alone. Observed call prices cluster in the $0.002–$0.03 band — price a lookup like a lookup.

Should I charge per call or a subscription?

Match the buyer. Subscriptions fit steady human buyers — a product team that wants predictable billing, an API key, and monthly invoices; hosted marketplaces meter usage through a gateway key on top. Pay-per-call fits autonomous agents and bursty traffic, where forcing a card through a signup form kills the sale. Most earning servers combine both: a subscription with included usage plus per-call overage, or a free tier for distribution with a paid tier for SLAs and volume. Prepaid credits put you in the business of holding other people's money; API keys with invoicing are the slowest path to cash and only make sense in enterprise procurement.

How does VibeFuse fit into selling MCP servers?

VibeFuse is the buyer-side harness: Settings → Tools hosts branded MCP cards (Google Workspace, Drive, GitHub, Copilot, Discord, Linear) plus custom stdio servers, all exposed to the built-in agents — a free desktop where every connected tool is one click away. The VibeFuse marketplace itself pays creators a flat 80% revenue share via Stripe Connect on widgets, skills, and styling packs ($0.50–$500 creator-set pricing, no listing fee). MCP servers are the tool-integration layer of that same canvas economy: the first ever free widget-based AI harness, local/offline processing, works in any app — with an open-source marketplace where creators make money on what they build.