Skip to content
RuleSellBeta
Sign up

Topic · A2

Paid MCP Servers: The New Category That Doesn't Have a Directory Yet

Under 5% of MCP servers are monetized. No canonical directory of paid ones exists. MCPize takes 15%, AgenticMarket promises 10%, xpay 5%. Here's the live category map.

# Paid MCP Servers: The New Category Under 5% of MCP servers charge money. There is no canonical directory of the paid ones. The market average price is still $0, which means almost every conversation about "monetizing your MCP server" is happening among people who haven't had a buyer yet. That's worth saying clearly because the category is real, growing, and underbuilt. PulseMCP's Pricing the Unknown post is the most-cited write-up of a creator actually charging for one — and the comments on it are the most honest pricing discussion in the space. This page is the live map. The platforms charging take rates. The creators charging for servers. The pricing models we've seen work. The category errors we've watched repeat.

The four-platform map

As of 2026 there are four serious monetization platforms aimed at MCP creators. Take rates and feature sets vary; trust and discovery signals matter more than take rate at this scale. | Platform | Take rate | Strength | Where they're weak | |---|---|---|---| | MCPize | 15% (85/15) | Cleanest creator UX, OAuth handled | Coverage; low buyer awareness | | AgenticMarket | 10% (90/10) | Most creator-favorable on rate | Newer, smaller catalog, less proven | | xpay | 5% (95/5) | Cheapest take rate | Infra and tooling less mature than MCPize | | RuleSell | 15% (85/15) | Discovery + verification + ratings; not just storefront | Newest in this specific lane (we ship MCP server monetization on top of the existing creator economy) | The 15% number isn't accidental. It's the App Store / Substack zone — high enough to fund moderation and security review, low enough that creators don't feel taxed. The 5% and 10% positions exist primarily as wedge pricing; we'd watch whether their infra and audit story holds up over the next 12 months. Source for take rates: Dev.to: "Pricing an MCP Server in 2026".

Who's actually selling MCP servers

We could list a dozen indie creators. Three patterns matter. Vertical-data servers. Paid market data wrapped in MCP. Paid legal research adapters. Healthcare API wrappers that already require licensing on the data side. The MCP layer here is a thin client over data the buyer was already paying for; the buyer is happy to pay the extra dollar to get it into their agent. Specialized vendor servers. Stripe's MCP server is free (it's a customer acquisition tool). But the category-defining example is plausibly Composio — they're not selling individual servers, they're selling a runtime that hosts 1,000+ tools through a single MCP endpoint with usage-based pricing. Composio bills the buyer; the buyer doesn't think of it as buying MCP servers, they think of it as buying Composio. Indie creator servers. Rarer. PulseMCP's "Pricing the Unknown" post is the canonical example — a developer trying $19/month on a specialized server and writing about whether anyone pays. The honest answer in 2026 is "some do, not enough to live on." This will change as the category matures.

Pricing models we've seen

Four pricing shapes in the wild. None is dominant yet. 1. Flat monthly subscription. Common. $9–$49/month. Works for vertical-data servers where the buyer values continuous access. 2. Per-call metered. Common for vendor servers (Composio's model). Aligns cost to use; harder to budget for buyers, easier to justify by ROI. 3. License key, perpetual. Less common. A one-time fee for unlimited use. Works for specialized servers a team installs once and uses forever; doesn't fund ongoing maintenance well. 4. Free + paid tier. The classic SaaS shape, slowly arriving in MCP. Free for hobbyists with rate limits; paid for production use. Notion's free tier vs. Notion Plus' MCP capabilities are the closest mainstream example we've seen.

Where this fails

Three honest places the paid-MCP category is still raw. 1. Buyer awareness is low. Most working developers don't think to look for a paid MCP server because the assumption is "MCP servers are free, open source, on GitHub." Until directories surface paid servers next to free ones (which means a directory we don't have yet — see the next section), discovery is the bottleneck. RuleSell is one bet on solving this. We're not the only possible answer. 2. Trust signals haven't standardized. What does "verified" mean for a paid MCP server? Pinned versions? Security disclosure? A SOC 2 report? Signed releases? Some combination of those? We push hard on this on /topic/mcp-security, but the industry hasn't converged on a checklist. 3. The "MCP middleman" risk is real. A creator who builds a paid wrapper around a free underlying API is one upstream price change away from being commodity. The most defensible paid servers are ones where the value is in the data (you actually licensed it) or in the workflow logic (you actually built non-trivial business code) — not in being the thinnest possible adapter.

Why no canonical directory exists yet

Three structural reasons. Anthropic's registry is metadata-only. The official registry.modelcontextprotocol.io is, by Anthropic's own description, "metadata and infrastructure" — they explicitly invite downstream marketplaces to "build search, browsing, and curation features on top of it." Pricing isn't part of registry metadata. Existing directories chose listings over commerce. mcp.so, Glama, Smithery, mcpmarket.com all list servers. None of them filter by price. None of them surface "is this server $0 or $19/month" in their search UI. Adding that would mean becoming a marketplace, not just a directory — a different business with different operational requirements. The category is small enough to overlook. Under 5% of servers means a 1,000-paid-server universe out of a 23,451-server catalog. Listicle-style content doesn't surface it. Directory search ranking doesn't surface it. Until paid servers cross some critical mass (we'd guess 2,000–3,000 paid servers), they're an editorial discovery problem, not a SEO surface problem. The opportunity is precisely the gap. RuleSell sits in the gap; so does anyone who builds an honest pricing-aware directory next.

What a working "paid MCP server" looks like in practice

Three concrete examples worth studying — not endorsements, references. Composio. Not sold as "paid MCP servers" but as a platform — 1,000+ toolkits exposed through a single hosted endpoint, usage-priced. Buyers don't think about individual servers; they think about tools they can call. The pricing surface is a Composio dashboard, the security surface is Composio's SOC posture. Closest thing to a turnkey paid experience the category currently has. Vendor-paid integrations bundled with a paid product. Linear's MCP server is free; the Linear subscription is paid. Same for Notion, Stripe, Sentry, Atlassian. This is the dominant monetization model today — the MCP server is a feature of the paid platform, not a standalone purchase. If you already pay $10/user/month for Notion, you're already a paid-MCP user; you just don't think of it that way. Indie creators charging directly. The PulseMCP "Pricing the Unknown" example. A specialized server, a $19/month price point, a creator willing to write publicly about whether anyone buys it. The candor in that post — including admitting the buyers haven't materialized at the volume expected — is the most useful primary source in the category. If you're thinking of selling an MCP server, read it before you write a pricing page.

What to read next

  • /for/claude-code — Claude Code is where most paid-MCP buyers configure their stack.
  • /for/cursor — Cursor's MCP support is feature-equivalent and growing.

Sources

Related GitHub projects

@PrefectHQ

fastmcp

🚀 The fast, Pythonic way to build MCP servers and clients.

⭐ 25,132

Frequently asked

Are there paid MCP servers?
Yes, but fewer than 5% of the catalog. A Dev.to founder writeup ('Pricing an MCP Server in 2026') estimates the share at under 5% — and notes the market average price is still $0. PulseMCP's editorial 'Pricing the Unknown' post is the canonical reference for the category's existence. The early monetized examples cluster in vertical data (legal research, market data, healthcare adapters), code/dev tools (Composio, mintmcp), and niche productivity (paid Notion integrations).
What's the revenue share on monetization platforms?
MCPize takes 15% (85/15 creator-favorable). AgenticMarket promises 90% to the creator (10% platform). xpay charges 5% (95/5). RuleSell's split is 85/15. Note these are platform fees on revenue, not the underlying MCP server's pricing — that's set by the creator. None of these platforms have hit the scale where their take-rate dominates the decision; coverage and trust signals do.
Is there a directory of paid MCP servers?
No canonical one. As of mid-2026, the official modelcontextprotocol.io registry is metadata-only and doesn't surface pricing. mcp.so, Glama, Smithery, PulseMCP, and mcpmarket.com all list servers without a 'paid' filter. RuleSell is building the directory we wanted to find — pricing, take rate, payment flow, and verification — but we'd happily lose the position to anyone with a more honest map.
Who would pay for an MCP server?
Three buyer profiles emerging in 2026. (1) Agencies and consultancies that need vertical data their clients pay for anyway — paid market data, paid legal research, paid healthcare APIs wrapped in MCP. (2) Solo developers who want one excellent specialized server instead of stitching three free ones. (3) Companies running agentic workflows in production where 'free, community-maintained, sometimes breaks' is unacceptable. Categories one and three are the ones with budget.
How does payment actually work — does the LLM hand over my credit card?
No. The buy and the call are separate. You purchase a license to the MCP server (or a subscription), receive an API key or OAuth credential, and configure your client to authenticate with it. The LLM never sees the payment surface. Stripe's own MCP server can be used to build the billing flow if you're a creator — see docs.stripe.com — but the protocol itself doesn't carry payments.
Should I trust a paid MCP server more than a free one?
Sometimes, with caveats. A paid server has a maintainer with revenue motivation to fix bugs and keep security current — that's real. It also has a financial incentive to keep you locked in, and the security-team-of-one problem doesn't go away just because someone is charging $19/month. Look for the same signals you'd look for on a free server: signed releases, a security.md, a real address, response time on issues. Paid does not equal vetted.

Related topics