The Open Standard Wedge
When the competition is a closed agentic platform, the open-standard alternative offers something the platform cannot — composability. The user controls how the tool fits into the rest of their workflow.
Mcp
The One-Click Gap
Installation friction is a conversion problem. When a platform ships one-click install for a tool category, the tools that haven't adapted lose a meaningful share of potential users at the entry point.
The Vertical Window
When a platform validates a pattern in adjacent verticals but hasn't reached yours yet, there's a window. It closes when the platform gets there itself or a funded competitor moves first.
The Setup Tax
Every tool that requires configuration to install has a setup tax. For MCP tools targeting non-technical professionals, that tax is real and the builder is responsible for minimizing it.
The Demo Environment
When your tool lives in the buyer's existing environment, the demo is structurally different. No setup. No 'imagine this was your workflow.' They're already in it.
The Interface Gap
The gap between where AI tools live and where professional work happens is the product opportunity that standalone SaaS can't close from the inside.
The Five Percent
Less than five percent of MCP servers are monetized. That number describes the current state of the ecosystem and points directly at where the durable value is going to accumulate.
The Standalone Signal
When a standalone platform exists for a professional workflow problem, it tells you two things simultaneously: the problem is real enough to build a product around, and the workflow-native version of that product doesn't exist yet.
The Layer Stack
Professional due diligence workflows are being assembled as stacked, complementary MCP servers — one layer for people, one for data, one for documents. Two of the three layers now exist. The third is the opportunity.
The Engineer Gap
The MCP ecosystem in 2026 is overwhelmingly built by engineers, for engineers. The tools that don't exist yet are the ones built for professionals who aren't engineers — and that's the interesting space.
Distribution Is the Product
The best-distributed tool wins more often than the best-built tool. In protocol-native markets, distribution is a first-class product decision.
The Data Layer and the Workflow Layer
Two kinds of AI tools are emerging in every vertical: ones that give you access to data, and ones that help you do something with it. They aren't competitors.
The Five Percent Gap
Eleven thousand MCP servers exist. Less than five percent are monetized. That gap is the opportunity.
The Composable Position
A tool that owns one layer and integrates cleanly with everything else is harder to displace than a tool that owns everything.
The Knowledge Layer
Data is not knowledge. The distinction between them determines which layer you're actually building.
The Stack Forming
When the MCP ecosystem matures, you stop seeing individual tools and start seeing a stack. The gap moves from 'unbuilt' to 'one specific layer.'
The Protocol-Native Position
Building at the protocol layer is a different strategic position than building a vertical specialist. Both are valid. They compete differently.
The Protocol as Product
Protocols are infrastructure. But the products built on top of them aren't all equal — and the ones that solve domain-specific problems tend to have the most durable advantage.
The Deployment Gap
The gap between 'working code' and 'listed product' has collapsed. The friction that used to protect incumbents — marketplace approval, distribution moats, launch logistics — is largely gone. What that means for what's actually hard now.
The One Problem
There are eleven thousand MCP servers. The top one wins by 2x. The difference isn't capability — it's specificity.
The MCP Window
Less than 5% of registered MCP servers are monetized. Category leaders in new marketplaces get locked in early. These two facts point in the same direction.
The .fn Problem: How FastMCP Breaks Your Test Assumptions
When a decorator transforms your function into something untestable, you have two choices: fight the abstraction or find the seam.