VirtualSMS MCP — SMS Verification for AI Agents

VirtualSMS is an account verification platform for developers and AI agents. It combines one-time SMS verification, dedicated number rentals, matching-country proxies and private cloud browser sessions behind one API, one MCP server and one prepaid balance.

Infrastructure for AI agents that need real-world phone verification.

The numbers are carrier-issued mobile numbers, backed by real physical SIM cards on carrier networks, not VoIP, which is why they pass the line-type checks that reject VoIP numbers at signup.

- receive one-time SMS codes from $0.05
- rent dedicated numbers from 1 to 30 days
- buy matching-country residential, mobile and datacenter proxies
- launch private cloud browser sessions that work alongside your number and proxy (beta)

All four work together from one prepaid balance, one API and one dashboard. Use only the pieces you need, or combine them into a single verification workflow.

Most providers solve one piece of the verification workflow. VirtualSMS combines numbers, rentals, proxies and cloud browser sessions behind one API, SDKs and an MCP server, so you use only the pieces you need or combine them into one workflow.

VirtualSMS can be used by individuals manually, integrated into applications with SDKs and APIs, or driven by AI agents through MCP. Use the platform through a REST API, official SDKs for Node, Python, PHP, Ruby and .NET, a hosted MCP server, or automation tools like n8n.

This server exposes that platform to any MCP client. Built for AI agents. Designed for agentic workflows. Works with Claude Code, Claude Desktop, Cursor, Windsurf and every MCP-compatible client, with no wrapper code to write.

Paste this into your MCP client's config. Nothing to install, no Node.js required on the client:

{ "mcpServers": { "virtualsms": { "type": "streamableHttp", "url": "https://mcp.virtualsms.io/mcp", "headers": { "x-api-key": "vsms_your_api_key_here" } } } }

"Buy me a Telegram number in the cheapest country and wait for the code."

Prefer to run it locally over stdio instead:

Verifying an account should not mean stitching together numbers from one provider, proxies from another, and browser sessions from a third: multiple accounts, multiple balances and APIs, and support spread across vendors. VirtualSMS brings those pieces together behind one balance, one API and one MCP server.

VirtualSMS combines all three under one account, and gives you one way to drive them:

Concrete jobs this server does today. Every one is a plain-English request your agent turns into tool calls:

Every client runs the samenpx virtualsms-mcpstdio command. Only the file location and format differ. The hosted config above works anywherestreamableHttpis supported and is the recommended path.

Edit~/Library/Application Support/Claude/claude_desktop_config.json(macOS) or%APPDATA%\Claude\claude_desktop_config.json(Windows):

claude mcp add --scope user virtualsms npx virtualsms-mcp -e VIRTUALSMS_API_KEY=vsms_your_api_key_here

40 tools by default. SetVIRTUALSMS_ENABLE_SESSIONS=1to expose 3 more.

Tool names are shown below without thevirtualsms_prefix for readability. The real wire names are prefixed:virtualsms_create_order,virtualsms_get_sms, and so on.

The core SMS verification surface: discover a service, price it, buy a number, get the code.

get_smsvswait_for_sms:wait_for_smsis the recommended default for interactive agent workflows. It blocks and returns the moment the SMS arrives over WebSocket. Useget_smsfor batch jobs, cron-driven polling, or when you already manage your own polling loop.

wait_for_smstakes anorder_id, not a service and country.Callcreate_orderfirst, then pass the returnedorder_id. That is the two-step buy-and-wait flow.

Keep a number by the day instead of buying a single verification. Two tiers:

- Full Access:local SIM inventory, for a whole number that works across any service. Every country in stock today lists 1, 7 and 30 days, at prices that vary per country. Durations and prices are not hardcoded here on purpose: callrentals_availablefor the live list per country and treat that as authoritative.
- Platform:sourced via our global supplier network, locked to one chosen service, durations of 1, 3 or 7 days. Callrentals_pricefor the exact retail price of a (service, country, duration) combo.

Stock, durations and pricing all differ per tier and per country, so callrentals_availablebefore committing to either. An active rental can be extended withextend_rentalat the current catalog price, in the same durations its tier allows.

Both tiers carry the same refund terms: cancel for a full refund within 20 minutes of purchase and before the first SMS arrives. Platform cancels are additionally subject to a 2 minute minimum hold, so a cancel inside the first 2 minutes is rejected and has to be retried.

Matching-country proxies, so the number and the IP agree. Three pools: residential, mobile and datacenter. Buy traffic by the GB, then generate a connection string.

Served only whenVIRTUALSMS_ENABLE_SESSIONSis set to1,trueoryes. Not exposed on the default surface.

create_order(service: "telegram", country: "US") → {order_id: "abc123", phone_number: "+14155552671", status: "pending"} wait_for_sms(order_id: "abc123", timeout_seconds: 180) → {success: true, code: "12345", delivery_method: "websocket", elapsed_seconds: 8}

How do AI agents receive OTP codes automatically?

Two tool calls.create_orderbuys a number for a given service and country and returns anorder_id.wait_for_smsthen blocks on thatorder_idand returns the moment the code arrives, pushed over WebSocket, typically in 2 to 15 seconds. The agent never polls, never sleeps in a loop, and never needs a human to read a phone. If you would rather drive your own loop,get_smspolls a single order instead.

Twilio is a full communications platform: send and receive SMS and voice, long-lived numbers, A2P campaigns, the lot. VirtualSMS does one job, which is receiving verification codes on demand. The practical differences:

- Line type.Twilio numbers are VoIP. Many services reject VoIP numbers at signup. VirtualSMS numbers are real physical SIM cards on carrier networks, so they resolve as mobile.
- Pricing shape.Twilio bills you for a number every month whether you use it or not. VirtualSMS bills per code from $0.05, with no subscription.
- Direction.Twilio sends and receives. This receives.

If you need to send messages, use Twilio. If you need to receive a verification code, this is purpose-built for it.

Why real physical SIM cards instead of VoIP?

Verification systems check the line type of the number you give them. VoIP numbers are cheap and disposable at scale, so they correlate with fraud, and a large share of services reject them outright at signup. Real physical SIM cards sit on carrier networks and resolve as mobile, which is exactly what those checks are looking for: a non-VoIP number that behaves like a real handset.

You do not have to take that on faith.check_numberruns a carrier and line-type lookup on any E.164 number, needs no API key, and will tell you whether a number reads as mobile, landline or VoIP.

Developers searching fortextverified mcp,sms-activate mcp,5sim mcp,daisysms mcporsmspool mcpare usually asking one question: which SMS verification provider can an AI agent drive natively? This section answers that without a scoreboard.

VirtualSMSpublishes this MCP server, so any MCP client calls it directly with no wrapper code: 40 tools, 2500+ services, 145+ countries, from $0.05 per code, on real physical SIM cards, plus number rentals and matching-country proxies from the same balance.

SMS-Activateshut down in December 2025. If your integration pointed there, it is gone, and the migration is a new API key and a new base URL rather than a rewrite: the shape of the job, buy a number then read the code, is the same here.

TextVerified,5SIM,DaisySMSandSMSPoolare all active SMS verification providers, each with its own API, pricing, coverage and terms. Check their current documentation for what they offer today.

We deliberately do not publish a comparison table of competitors' prices, service counts or coverage. Those numbers move week to week, we have no privileged view into anyone else's inventory, and a stale table dressed up as research is worse than no table at all. The VirtualSMS numbers above are ours and we stand behind them. Compare them against whatever you are using now.