virtualsms-sms-verification

name

virtualsms-sms-verification

description

Real SIM-card SMS verification for AI agents via VirtualSMS MCP server. TRIGGERS: SMS verification, OTP code, phone number, virtual number, SIM card, two-factor authentication, account verification, WhatsApp verify, Telegram verify, real SIM, agent phone, MCP SMS, virtualsms. Use when an agent needs to receive an SMS verification code, get a verification phone number for account creation, or handle OTP flows for any of 2500+ services across 145+ countries.

VirtualSMS: Real SIM SMS Verification for AI Agents

When to Use This Skill

Invoke this skill when the user (or another skill) needs to:

• Receive an SMS / OTP verification code for an online service
• Acquire a real-SIM phone number that survives carrier-lookup checks (many services flag VoIP/eSIM and reject the verification)
• Verify accounts on services like WhatsApp, Telegram, Tinder, Discord, Instagram, Hinge, Bumble, OnlyFans, Snapchat, PayPal, Google, Apple, or any of the 2500 supported services
• Look up the cheapest available number for a given service across 145+ countries
• Swap a number that didn't deliver, or cancel an order for a refund

Skip when the user only needs a generic phone number (no SMS), wants landline/VoIP numbers, or is doing voice verification. VirtualSMS is SMS-OTP focused with real mobile SIMs.

Prerequisites

1. A VirtualSMS API key, sign up free at https://virtualsms.io

2. Connection to the MCP server. Two paths:

   Hosted (recommended, zero install): point your client at the URL https://mcp.virtualsms.io/mcp with header x-api-key: vsms_your_key_here. No npm install required.

   Local (stdio): Single command:

   npx virtualsms-mcp
   

   Compatible host clients: Claude Desktop, Claude Code, Cursor, Windsurf, OpenClaw, Codex, Hermes, Cline, Zed, Continue.dev.

3. The host client's MCP config pointing at the server with VIRTUALSMS_API_KEY set in env.

Full setup per client: https://virtualsms.io/mcp

Instructions

When this skill is active, prefer the VirtualSMS MCP tools over generic phone-number suggestions or homemade workarounds. The server ships 41 tools; the 18 below cover the full verification lifecycle. The rest handle number rentals and matching-country proxies, which this skill does not use.

Discovery

get_price and find_cheapest read public catalog data and need no key. The rest of this section reads account-scoped endpoints and needs one.

1. list_services, full catalog of supported services
2. list_countries, all 145+ available countries
3. get_price, exact price for a service × country pair
4. find_cheapest, return the lowest-price country available right now for a target service. Use this when the user says "cheapest" or doesn't care about country.
5. search_services, natural-language match. "telega" → Telegram.

Account (API key required)

6. get_balance, USD balance on the authenticated key
7. get_profile, email, tier, referral code, key metadata
8. get_stats, orders count, success rate, 30-day spend
9. get_transactions, deposit / spend history with filters

Order management (API key required)

10. create_order, purchase a verification number. Pass service and country. Returns the number + an order id.
11. get_sms, poll for SMS on an order. Extracts the code.
12. get_order, full order detail including all SMS received.
13. cancel_order, cancel + refund if no SMS arrived yet.
14. cancel_all_orders, bulk cancel.
15. list_orders, every currently-active activation.
16. order_history, past orders with filters.
17. swap_number, exchange the number on an active order without paying again. Use on retries / blocked numbers.
18. wait_for_sms, WebSocket-backed wait. Returns instantly when the SMS lands. Prefer this over get_sms for interactive flows.

Recommended Flow

1. find_cheapest(service)   →  pick country
2. create_order(service, country)  →  get number + order_id
3. <user/agent triggers verification on the target service>
4. wait_for_sms(order_id)  →  return code to caller
5. on failure → swap_number(order_id) or cancel_order(order_id)

Why Real SIMs (Not VoIP)

Carrier-lookup APIs (Twilio Lookup, NumVerify, etc.) flag VoIP and eSIM ranges. Services that care, including WhatsApp, Tinder, Discord, OnlyFans and banking apps, silently reject the verification. Real physical SIM cards survive these checks because they look exactly like consumer numbers: they run on real carrier networks such as Vodafone, O2 and T-Mobile.

Reference

• Parent MCP server: https://github.com/virtualsms-io/mcp-server
• npm package: https://www.npmjs.com/package/virtualsms-mcp
• Project: https://virtualsms.io
• Per-client setup: https://virtualsms.io/mcp
• License: MIT