← back to mcp-tool-call-gating-proxy
Financial analysis · adoption-ready estimate
MCP Tool Call Gating Proxy ·
If an entrepreneur "adopted" this product today, here's the realistic math.
Fermi summary
Land 45 paying teams at $300/mo and you hit $162k ARR - honest odds are about 13% you pull that off in year 1, and you'll burn ~$28k getting there regardless.
Market size (TAM)
$20.0M
~5,000 companies actively deploying MCP agents in production with compliance or security requirements × ~$4,000 avg annual spend on AI agent governance tooling
Year-1 ARR range
$24k - $480k
midpoint $160k
Investment to production
$28k
Dev: $14k for hardened auth, billing, policy DSL, audit log UI. Docs/DX: $4k for integration guides and CLI tooling. Outbound marketing: $7k
Probability of success
13%
P(reaching mid case in 12 months)
Expected take-home Y1
$-9904
probability-weighted, after investment
Go-to-market motion
Developer-led bottom-up via MCP community, GitHub, and Hacker News → free tier with quota → upgrade to $200-500/mo per team when audit logging or policy rules hit limits → occasional enterprise pilot at $1,500-3,000/mo.
Key risks
- Anthropic ships native tool call permissioning in their API or Claude.ai platform, eliminating the core value prop with zero notice
- MCP-supporting clients (Cursor, VS Code, Windsurf) build gating natively into their agent runtimes, bypassing third-party proxies entirely
- Developer buyers have very high DIY tolerance - OPA policies, custom middleware, or a weekend hack feels sufficient for most teams until their first incident
- Enterprise procurement requires SOC2 Type II before signing any security-adjacent tooling contract, which takes 6-12 months and $15-25k to obtain
Generated by the Wishdeal Factory financial-analysis agent. Numbers are honest Fermi estimates, not guarantees. Real outcomes depend on the operator. The studio is bullish on the engineering quality, agnostic on the business outcome.