Drop-in OpenClaw skill for a full account verification workflow: real-SIM numbers, rentals, matching-country proxies and cloud browser sessions, shared across every agent.
TL;DR
Account verification for OpenClaw: 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 OpenClaw to the VirtualSMS MCP server: six capabilities live on day one.
Drop the skill into your OpenClaw skills directory, every agent on the workspace inherits the tools.
Standard MCP stdio transport, no custom OpenClaw shim required.
40 tools (18 activation & account | 9 rentals | 10 proxy | 3 other). Several are unique to VirtualSMS, including find_cheapest and wait_for_sms.
Real physical SIMs across 2500+ services and 145+ countries, not VoIP, not eSIM.
API key lives in the workspace env, agents never see it directly.
Same backend as the dashboard and REST API. Switch surfaces with no data migration.
Zero install. Paste the block into your OpenClaw MCP settings, plug in your VirtualSMS API key, restart.
Claude
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.
{
"mcpServers": {
"virtualsms": {
"command": "npx",
"args": ["-y", "virtualsms-mcp"],
"env": {
"VIRTUALSMS_API_KEY": "your_key_here"
}
}
}
}OpenClaw speaks standard MCP over stdio. Add the block above to your OpenClaw workspace's MCP config and set VIRTUALSMS_API_KEY in the workspace env. Restart the workspace and the 40 tools appear in every agent.
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 OpenClaw 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 OpenClaw skill, out of 2500+ supported services on the same backend.
Source, install instructions, and example OpenClaw sessions. MIT-licensed. PRs welcome.
Open on GitHubType these straight into OpenClaw, no tool names required.
FAQ
It is virtualsms-mcp, packaged as a Skill so OpenClaw users can install it the same way they install other Skills. Same npm package, same tools, same auth. The Skill wrapper just standardizes the install path so multi-agent workspaces inherit the tools without per-agent setup.
No. The key lives in the OpenClaw workspace env. Every agent in that workspace shares the key, and the spend rolls up to one VirtualSMS account. For per-agent isolation, create separate workspaces with separate keys.
Yes. create_order, cancel_order, swap_number all run without user prompt by default. Wrap them in your OpenClaw policy if you need approval gates. cancel_order is fully refundable until an SMS arrives, so most workflows ship without gates.
120 requests per minute per API key. That covers every interactive multi-agent workflow we have seen. Need more? Email support, we raise limits for production accounts.
The same install exposes the full platform: one-time SMS verification, dedicated number rentals (1 to 30 days), matching-country residential, mobile and datacenter proxies, and private cloud browser sessions (beta, invite-only). All 40 tools share one API key and one prepaid balance, so there is nothing extra to configure per capability.
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