One-line install that gives Claude Code and Desktop a full account verification workflow: real-SIM numbers, rentals, matching-country proxies and cloud browser sessions, not VoIP.
TL;DR
Account verification for Claude: SMS, rentals, proxies and cloud browser, one prepaid balance.
Show full summary
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.
From one prepaid balance you can:
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.
One drop-in skill that wires Claude to the VirtualSMS MCP server: six capabilities live on day one.
List services, countries, and live prices from chat, no dashboard hop.
Order activation numbers (one-time SMS) with a typed natural-language prompt.
WebSocket-backed wait_for_sms: the SMS arrives in chat the moment the carrier delivers.
Rent a number for 1 to 30 days, or buy a matching-country proxy and a private cloud browser session (beta), from the same balance.
Swap a flagged number for a fresh one with no extra charge.
Read account balance, history, and stats, same auth, same bill.
Zero install. Paste the block into your Claude MCP settings, plug in your VirtualSMS API key, restart.
Perplexity
Gemini
{
"mcpServers": {
"virtualsms": {
"type": "streamableHttp",
"url": "https://mcp.virtualsms.io/mcp",
"headers": { "x-api-key": "vsms_your_api_key_here" }
}
}
}
Hosted at https://mcp.virtualsms.io/mcp.
Same 40 tools as the npm package, no Node required.
Prefer running stdio locally? Same backend, same auth: npm-installed instead of hosted.
claude mcp add --scope user virtualsms -- npx -y virtualsms-mcp -e VIRTUALSMS_API_KEY=your_keyInstalls at user scope so the Skill loads in every Claude Code project. For Claude Desktop, paste the standard mcpServers block into claude_desktop_config.json instead, same env var, same package.
Replace your_key_here (stdio) or
vsms_your_api_key_here (HTTP) with a key from
Settings > API Keys
or sign up free.
The numbers are carrier-issued mobile numbers, backed by real physical SIM cards on operators like Vodafone, O2 and T-Mobile, not VoIP, so they pass the line-type checks that reject VoIP at signup. Each number lives on a real handset on a real carrier. WhatsApp, Telegram, Google, Discord and 2500+ other services accept these numbers because they pass carrier_lookup checks, the API every modern verification provider runs to filter out VoIP and eSIM pools.
VoIP and eSIM-only numbers fail those checks and bounce at signup, so your Claude agent never wastes budget on a number that cannot deliver.
That is the entire pitch: real numbers, real delivery. Verifications from $0.05, full refund if no SMS arrives. The same MCP server also rents numbers for 1 to 30 days, sells matching-country proxies, and runs private cloud browser sessions (beta), all from the same balance.
Twelve of the most-requested verification surfaces work today through the Claude skill, out of 2500+ supported services on the same backend.
Source, install instructions, and example Claude sessions. MIT-licensed. PRs welcome.
Open on GitHubType these straight into Claude, no tool names required.
FAQ
Both. The Claude Code CLI command above is the fastest install. For Claude Desktop, paste the JSON config into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\, Linux: ~/.config/Claude/) and restart the app.
All of it. The Skill installs the full virtualsms-mcp server: one-time SMS verification, dedicated number rentals for 1 to 30 days, matching-country proxies, and private cloud browser sessions (beta), all from one API key and one prepaid balance. 40 tools total (18 activation & account | 9 rentals | 10 proxy | 3 other).
Yes. Numbers come from real physical SIM cards on operators like Vodafone, O2, T-Mobile and Lebara. WhatsApp, Telegram, Google, Discord and 2500+ other services accept them. VoIP and eSIM pools fail those checks, we do not use them.
wait_for_sms is WebSocket-backed: it returns as soon as the carrier delivers the SMS. End-to-end latency is typically 5-30 seconds. No polling loop, no rate-limit risk.
No. Tool calls bill the same as REST API or dashboard usage, activations from $0.05. Anthropic does not surcharge for MCP, and VirtualSMS does not surcharge for the Skill surface.
Looking for the full MCP setup across every client?
Run a blog, tool list, or Telegram channel? Earn up to 15% lifetime commission.
Become an affiliate