VirtualSMS — SMS Verification API for AI Agents & Developers

Created By
VirtualSMS3 months ago
VirtualSMS is an SMS verification API for developers and AI agents. Buy virtual phone numbers and receive OTP codes for 700+ services including Telegram, WhatsApp, Google, Facebook, Twitter, TikTok and more in 100+ countries. Real SIM cards — not VoIP — means higher success rates. Full refund guaranteed if no SMS received. Includes MCP server for Claude/Cursor, REST API, and Telegram bot. Pay-per-use pricing with no subscription required.
Overview

VirtualSMS — SMS Verification for AI Agents & Developers

Buy virtual phone numbers and receive OTP codes instantly. Built for developers, AI agents, and anyone who needs reliable SMS verification at scale.

Why VirtualSMS?

  • Real SIM cards — not VoIP, higher success rates than competitors
  • Instant OTP delivery — WebSocket push, no polling delays
  • Full refund guarantee — no SMS received? Get your money back automatically
  • 700+ services — Telegram, WhatsApp, Google, Facebook, Twitter, TikTok, Instagram, and more
  • 100+ countries — US, UK, Russia, India, Brazil, and more
  • Pay-per-use — no subscription, no monthly fees

Use It Your Way

🤖 MCP Server (AI Agents)

Use directly inside Claude, Cursor, Windsurf, Cline, or any MCP-compatible AI agent. Buy numbers, wait for OTPs, cancel orders — all from natural language.

🔌 REST API

Full programmatic access. Check prices, buy numbers, poll for SMS, manage orders. Simple API key auth.

💬 Telegram Bot

Manual use without any code. Perfect for quick verifications on the go.

Supported Services (Sample)

Telegram · WhatsApp · Google · Facebook · Instagram · Twitter · TikTok · Discord · Amazon · Microsoft · Tinder · Uber · PayPal · Binance · Coinbase · and 700+ more

Perfect DaisySMS Alternative

DaisySMS is closing March 26, 2026. VirtualSMS offers the same virtual number service with better reliability, a modern API, and MCP support for AI workflows.

Quick Start

  1. Sign up free at virtualsms.io
  2. Add funds (crypto via NOWPayments)
  3. Get your API key at Settings → API Keys
  4. Buy a number via API, bot, or AI agent
  5. Receive your OTP instantly

Server Config

{
  "mcpServers": {
    "virtualsms": {
      "command": "npx",
      "args": [
        "-y",
        "virtualsms-mcp"
      ],
      "env": {
        "VIRTUALSMS_API_KEY": "<YOUR_API_KEY>"
      }
    }
  }
}
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
VirtualSMS
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Payai X402 Tools

2 hours ago
Payai X402 Tools

2 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago