Build or Skip

MCP infrastructure tools

We said BUILD on August 5, 2026. Not settled — due August 5, 2027.

Read this with the caveat. We tested the engine that produced this verdict against 292 launches whose outcomes we already knew, and could not show it predicted which survived. Some of its data sources were also dead at the time of scoring. The verdict stays up, dated and unedited, because a record you can quietly revise is not a record — but it is worth less than it looked when it was written.

The evidence shows genuine, growing B2B developer demand with several paying incumbents and a clear underserved niche: open-source, self-hosted, multi-cloud MCP infrastructure for small teams. It's winnable via an organic developer-reach wedge, but the protocol's volatility and dev monetization difficulty are real risks. Net: a legitimate BUILD with eyes open.

Was there demand

7out of 10

Multiple channels agree: growing search demand on commercial keywords, active Reddit/HN threads, and at least 5 competitors already monetizing MCP infrastructure. This is proven B2B/utility demand, not just chatter.

Could a builder win it

7out of 10

Incumbents are either enterprise-priced (Itential, K2view) or narrow (Firecrawl, Lunar.dev), leaving a clear open-source/self-hosted wedge for solo devs and small teams. Competition is medium and explicitly solo-beatable, and the buyer (developers) is reachable through organic channels like HN and Reddit.

The case against this verdict

MCP is a fast-moving, standards-driven space where the protocol owner (Anthropic) and well-funded infra players can absorb the open-source registry/toolkit wedge overnight, turning today's gap into a commodity feature. A solo founder risks building on shifting sand — the 'code execution instead of MCP' paper (80 upvotes) hints the primitive itself may be contested — and monetizing free-tier-hungry developers is notoriously hard.

Who was already there

  • AWS Cloud Control API MCPLocked into AWS ecosystem; steep learning curve; requires AWS credentials management; limited to AWS resources only
  • Itential MCP ServerEnterprise-focused pricing; complex setup; requires existing infrastructure knowledge; limited community resources
  • Firecrawl MCPNarrowly focused on web scraping/data extraction; not a general infrastructure tool; limited scope
  • Lunar.devPrimarily API traffic management; not full infrastructure; control plane complexity; requires integration work
  • K2view MCPData-centric focus; not general-purpose infrastructure; niche use case; less visible in MCP community

Other verdicts

What is worth more than this page. The register records what became of 6,266 real launches. No engine has to be right for that to be true.