Add one MCP block so Hermes runs a full account verification workflow inline: real-SIM numbers, rentals, matching-country proxies and cloud browser sessions, not VoIP.
TL;DR
Account verification for Hermes: 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 mcp that wires Hermes to the VirtualSMS MCP server: six capabilities live on day one.
Add one MCP server block to your Hermes config, every Hermes agent and subagent gains all 40 VirtualSMS tools: verification, rentals, proxies and cloud browser sessions.
Standard MCP stdio transport, no Hermes-specific shim, plugin, or adapter to maintain.
Hermes lists services, checks live prices, and buys numbers from a single natural-language turn.
WebSocket-backed wait_for_sms returns the SMS in the conversation the moment the carrier delivers.
Real physical SIM numbers across 2500+ services and 145+ countries, not VoIP, not eSIM.
cancel_order refunds in full if no code arrives; swap_number gets a fresh number at no extra charge.
Zero install. Paste the block into your Hermes 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"
}
}
}
}Hermes speaks standard MCP over stdio. Add the block above to your Hermes MCP servers configuration and set VIRTUALSMS_API_KEY in the environment. Restart Hermes, the 40 virtualsms tools register automatically, no custom integration required.
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 Hermes 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 Hermes mcp, out of 2500+ supported services on the same backend.
Type these straight into Hermes, no tool names required.
FAQ
Hermes is Nous Research's agent ("the agent that grows with you"). Any Hermes build with MCP support loads stdio MCP servers from its configuration, add the block above, set the API key, and restart. The 40 virtualsms tools then appear to the agent.
No. virtualsms-mcp is a standard MCP stdio server, the same npm package every MCP client uses. Hermes loads it like any other MCP server; there is no Hermes-specific shim to install or maintain. Prefer zero-install? Use the hosted StreamableHTTP endpoint above instead.
Yes. Numbers come from real physical SIM cards on operators like Vodafone, O2, T-Mobile and Lebara. WhatsApp, Telegram, Google, Discord and 2500+ other services accept them because they pass carrier_lookup checks. VoIP and eSIM pools fail those checks, we do not use them.
Yes. create_order, cancel_order and swap_number run without a prompt by default. Gate them behind an approval step in your Hermes policy if you need one. cancel_order is fully refundable until an SMS arrives, so most workflows ship without gates.
No surcharge. Activations bill from $0.05, the same backend, auth, and pricing as the dashboard and REST API. One VirtualSMS API key works across every surface; spend rolls up to one account.
Add the VirtualSMS MCP server above to your Hermes config and set VIRTUALSMS_API_KEY. Hermes can then call create_order to provision a real-SIM phone number on demand and wait_for_sms to read the incoming SMS, a working number for any verification, available to every subagent.
You don't need it to be. Hermes loads any standard MCP stdio server from your config, paste the block above, set your API key, restart, and the 40 virtualsms tools register like any other MCP server, whether or not it ships in the bundled catalog.
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