The SMS Verification Market is Bigger Than Most People Realise: Data from 67,000+ Virtual Phone Numbers

Quackr — Wed, 03 Jun 2026 06:54:46 +0000

We run Quackr, a virtual phone number platform that lets developers and individuals receive SMS verifications without exposing a real number. We just published our first inventory transparency report and the data was surprising enough that we thought the dev community would find it useful.

The Numbers

Right now, 97.6% of our entire virtual phone number inventory is actively rented. 66,214 out of 67,815 numbers assigned and in use across 15+ countries. Over 1,000 numbers available at any given moment but they move fast.

That utilisation rate tells you something about how the market has shifted. Virtual numbers are no longer a niche throwaway tool. Developers, businesses, and privacy-conscious users are holding them long term.

What Developers Actually Use Virtual Numbers For

The obvious use case is SMS verification during testing. Spin up a number, verify an account in staging, move on. But that is not what drives the bulk of demand on our platform.

The real volume comes from:

Multi-account management — developers and businesses running multiple instances of platforms that require unique phone verification per account.

Privacy layers in production apps — applications that need to verify users without collecting their real numbers. A virtual number sits between the user and the platform.

Automated verification pipelines — this is where our API and MCP Server come in. If you need to provision numbers programmatically and retrieve OTPs without manual intervention, this is the use case we built for.

Geographic flexibility — needing a UK number from Australia, a US number from Ukraine, or any combination that your real SIM cannot provide.

The OTP Blocking Problem

Something worth knowing if you are building anything that involves SMS verification: platform-level VoIP blocking has become significantly more aggressive over the past two years.

WhatsApp, Telegram, Google, and TikTok all run detection on incoming verification requests. A VoIP number gets flagged and the OTP simply never sends. No error message. No explanation. The code just does not arrive.

Non-VoIP numbers — numbers tied to real carrier infrastructure rather than internet-based systems — bypass this entirely. This is the core technical distinction that drives purchasing decisions on our platform more than any other factor.

The MCP Server Angle

Something we built that the developer community has not fully discovered yet — we run an MCP server at quackr.io/mcp that lets AI agents provision real phone numbers programmatically.

If you are building an AI agent that needs to verify accounts, receive OTPs, or interact with any platform requiring SMS verification, you can give it a real non-VoIP number through our MCP integration. The agent provisions the number, the OTP arrives, the agent reads it. No human in the loop.

That use case is early but growing fast.

The API

If you need programmatic access to virtual numbers for any of the above use cases, our REST API handles number provisioning, SMS retrieval, and number management.
Full documentation at quackr.io/api.

For AI agent integrations specifically, the MCP server is the faster path — it exposes the same functionality in a format your agent can call directly without writing API wrapper code.

Full Report

The complete inventory transparency report with all the data is at quackr.io/blog. We will be publishing this monthly going forward as the numbers shift.

Happy to answer questions about the technical side of virtual number infrastructure, OTP blocking behaviour, or how to integrate SMS verification into whatever you are building.

Built by the team at Quackr — virtual phone numbers for SMS verification across 15+ countries.