VoidMob MCP Server: Phone Numbers, eSIMs and Mobile IPs as Agent Tools
Tallinn-based connectivity provider VoidMob highlighted its open-source MCP server on 30 October 2026: MCP-compatible AI applications can reach mobile proxy services, eSIM data plans and SMS tooling through one unified interface instead of integrating each service separately, with configurable spending controls
Features
- ✓ One MCP endpoint exposes mobile proxies, non-VoIP SMS, private dedicated numbers and eSIM data plans, so agents can order, rotate IPs and activate eSIMs themselves
- ✓ MIT-licensed and open source, with what the company describes as a free sandbox mode that needs no key, and pay-per-use from a prepaid balance afterwards
- ✓ Spend controls built for agents: per-order caps, a session budget and a read-only mode so a retry loop cannot quietly drain the wallet
- ✓ Setup paths documented for Claude Code, Codex, Cursor and Gemini CLI, with guides for OpenClaw, Hermes Agent and Grok Bot as well
- ✓ Aimed at the cloud-IP and virtual-number problem: real 4G/5G carrier IPs, non-VoIP operator numbers and eSIM coverage across 200+ destinations
How to Use
- Read the MCP documentation first and map the tools you need — proxy rotation, number rental, eSIM activation, balance and order checks are separate tools
- Start in sandbox mode with a read-only call to confirm your MCP client discovers and invokes the tools correctly before touching real balance
- Before production, hard-set the per-order cap and session budget, then run a failure-injection test in read-only mode to see whether the agent re-orders on retries
- Make purchasing an explicit confirmation step in the agent, and log order IDs and spend so the ledger can be reconciled afterwards
FAQ
What is VoidMob's MCP server?
Per the announcement published on 30 October 2026, VoidMob is a Tallinn-based mobile connectivity and proxy infrastructure provider whose open-source Model Context Protocol server lets compatible AI applications access mobile proxy services, eSIM data plans and SMS tools through a common interface, reducing per-service integration work. The release also mentions configurable spending controls. Repository at https://github.com/voidmobcom/voidmob-mcp and product page at https://voidmob.com/mcp
What licence and pricing apply?
The voidmob-mcp repository is MIT-licensed, and the company's blog describes a free sandbox mode requiring no key. The underlying service is pay-per-use from a prepaid balance with crypto top-ups. Note the distinction: open-source server code does not mean free resources — mobile proxies, SMS numbers and eSIMs still cost money
How many tools does it actually ship?
The published numbers disagree, so verify yourself: the GitHub repository describes 28 tools, the company blog says 30 tools, and the PulseMCP directory recorded 18 earlier. The toolset keeps evolving, so treat your own tools-list output after installation as the source of truth rather than planning around a blog figure
Why do agents need mobile IPs and real numbers?
The company's stated reason is that agents fail on cloud IPs and VoIP numbers: many sites apply risk controls to datacentre IP ranges and virtual numbers, which blocks signup, OTP delivery and page access. Mobile proxies supply carrier IPs and non-VoIP numbers can receive real SMS codes, which together let an agent complete signup-style tasks that need an identity and a network environment. This is a grey area — check the target site's terms of service and local law before relying on it
What goes wrong most often?
Runaway spend: agents re-order inside retry loops. Set small per-order caps and a session budget, watch behaviour read-only, and expand permissions gradually. Second is logging — order IDs, spend and which tool was called all need a trail or you cannot attribute failures. And keep these capabilities out of unattended long-running jobs; require human confirmation before payment