Paid MCP is still an overlay, not a core MCP feature

Paid MCP remains a market category rather than a single standard because the Model Context Protocol specification defines how tools are described and invoked but does not specify settlement, according to zFinia's 7 September 2026 retrospective. Cloudflare's gateway, x402 challenge-handoff, and MPP each propose hanging payment on the same tool call, but until the MCP spec itself names a payment profile, paid MCP stays an overlay rather than a core feature.

TIER A · unmet need Paid MCP is still an overlay, not a core MCP feature MCP specifies how tools are described and invoked. It does not specify settlement. Cloudflare’s gateway, x402 challenge-handoff and MPP all propose to hang payment on the same tool call. Until the MCP spec itself names a payment profile, “paid MCP” remains a market category, not a single standard. Event 1 July 2026 · source 1 July 2026 · zFinia published 7 September 2026 · retrospective Why it matters This is a high-intent buyer-hand-raise cluster: developers asking how to monetize MCP. Proven demand requires payments, not questions.