MCP started as a protocol for local tool integration. By 2026, hosted remote MCP servers are common — third-party services exposing capabilities to any agent that authenticates. The marketplace dynamics matter: who runs them, how they're discovered, what pricing models work.
Who hosts
Companies wrapping their existing API as MCP (Notion, Linear, Stripe MCP servers). Aggregators packaging many services. Marketplaces (Anthropic, Google, OpenAI offering directories). Each layer adds value at a different point.
Discovery
Marketplace listings (Anthropic, others). DNS-based discovery (.well-known/mcp endpoints). Manual configuration still dominant. No standard discovery in 2026; mostly point-to-point.
Pricing models
Free with rate limits, paid tiers. Per-call pricing. Subscription. Bring-your-own-API-key (server is a thin proxy that uses your underlying API quota). Each model fits different value propositions.
Trust and security
Trust the server with user data sent in tool calls. Trust the server's results to be incorporated into agent context (prompt injection vector). Verified servers (signed manifests, marketplace review) reduce risk; not eliminate.
What changes the picture
Standardized capability discovery. Server reputation systems. Industry-specific compliance certifications. The marketplace will mature; the 2026 picture is early-internet-shaped (vibrant but uneven). Plan for changes.