OpenClaw Skill for SMS verification
Plug-and-play OpenClaw skill that gives orchestrated agents real-SIM SMS verification with no per-agent setup.
Claude
Perplexity
GeminiWhat you get
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.
18 tools: discovery (5), account (4), order management (9). Four are unique to VirtualSMS.
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.
Quick install — Hosted MCP (HTTP)
Zero install. Paste the block into your OpenClaw MCP settings, plug in your VirtualSMS API key, restart.
{
"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 18 tools as the npm package, no Node required.
Generic MCP stdio config
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 18 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.
Why real SIMs (not VoIP or eSIM)
VirtualSMS provisions physical SIM cards on operators like Vodafone, O2, T-Mobile and Lebara. 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 numbers (Twilio, TextNow, Google Voice) and eSIM-only numbers fail those checks. The verification request bounces with a generic "this number cannot receive verification codes" error — so your OpenClaw agent burns budget on numbers that never deliver. Every number we sell is a carrier_lookup pass before it ever lands in your order.
That is the entire pitch: real numbers, real delivery. Verifications from $0.05, full refund if no SMS arrives.
Compatible services
Twelve of the most-requested verification surfaces work today through the OpenClaw skill. Plus 1,988 more on the same backend.
- Telegram
- Discord
- Signal
- X (Twitter)
- TikTok
- Snapchat
- Tinder
virtualsms-io/openclaw-skill-sms-verification
Source, install instructions, and example OpenClaw sessions. MIT-licensed. PRs welcome.
Open on GitHubOpenClaw FAQ
How is this different from registering virtualsms-mcp directly in OpenClaw?+
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.
Does each agent need its own VirtualSMS API key?+
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.
Can OpenClaw agents place orders autonomously without confirmation?+
Yes — buy_number, 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.
What is the rate limit per workspace?+
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.
Does this work with self-hosted OpenClaw?+
Yes. The Skill installs over stdio against the npm package; nothing in the integration depends on hosted OpenClaw infrastructure. Self-hosted, hosted, and hybrid deployments are all supported.
Real-SIM SMS verification MCP for humans and AI agents — works with Claude, Cursor, ChatGPT, Perplexity & Gemini · virtualsms-mcp v1.1.1 · last updated 2026-04-25
