VirtualSMS MCP — SMS Verification for AI Agents
@virtualsms-io
VirtualSMS MCP gives AI agents full SMS verification capability: discover prices, buy temporary phone numbers, and receive verification codes in real time via WebSocket push (with polling fallback). It includes 11 MCP tools for search, pricing, purchase, order management, and cod
Overview
What is VirtualSMS MCP?
VirtualSMS MCP Server is a Model Context Protocol (MCP) server that gives AI agents access to a complete SMS verification API. It allows agents to get virtual phone numbers, receive SMS online, and extract verification codes — all without leaving the AI workflow. Powered by VirtualSMS.io, which operates its own modem infrastructure across 200+ countries.
How to use VirtualSMS MCP?
Run npx virtualsms-mcp or install globally via npm install -g virtualsms-mcp. Obtain an API key from virtualsms.io and set the VIRTUALSMS_API_KEY environment variable. Configure the MCP client (Claude Desktop, Cursor, etc.) with the command and env variable. The server exposes 11 tools: discovery, account, and order management tools including wait_for_code for one-step SMS retrieval.
Key features of VirtualSMS MCP
- 11 MCP tools for SMS verification
- Real-time SMS delivery via WebSocket with polling fallback
- Operates on own SIM card infrastructure (not a reseller)
- Covers 200+ countries for phone numbers
- Supports migration from SMS-Activate or DaisySMS
- One-step
wait_for_codetool buys number and retrieves code
Use cases of VirtualSMS MCP
- AI agents verifying accounts on Telegram, WhatsApp, Google, Instagram, etc.
- Automated phone verification for 500+ online services
- Crash recovery for interrupted verification sessions
- Budget-aware SMS verification by first finding cheapest country
- Manual step-by-step verification with buy, check, and cancel flows
FAQ from VirtualSMS MCP
What does VirtualSMS MCP do?
It gives AI agents access to SMS verification using virtual phone numbers — agents can buy numbers, wait for incoming SMS, and extract verification codes programmatically.
How does VirtualSMS compare to SMS-Activate or DaisySMS?
VirtualSMS is a direct alternative with its own modem infrastructure, comparable service coverage, competitive pricing, and a modern API. Users only need to swap the API key and update the base URL; the core flow (buy number → wait for SMS → get code) is identical.
What runtime dependencies are required?
Node.js and npm are required. The server can be run via npx or installed globally with npm install -g virtualsms-mcp.
Where do phone numbers and SMS data reside?
Phone numbers and SMS are hosted on VirtualSMS’s own infrastructure — real SIM cards across 200+ countries. Data is accessed through their REST API and WebSocket endpoints.
What transports and authentication are used?
The MCP server communicates over stdio with the client. It connects to VirtualSMS via REST API and WebSocket for real-time delivery. Authentication is done using the VIRTUALSMS_API_KEY environment variable.
