VoidMob MCP puts phone numbers, mobile proxies, and eSIMs behind 28 agent tools

An agent that can browse, fill forms, and call APIs still stalls at a familiar step: the SMS code. The service will not proceed until a human provides a number that can receive it, and a VoIP number often will not work. VoidMob MCP is built around that gap. Its README describes it as real mobile infrastructure for AI agents — US non-VoIP numbers for SMS verification, private dedicated numbers, 4G/5G mobile proxies, and travel eSIMs, exposed as 28 tools and paid from a prepaid USD balance. The fastest way in is hosted. You add https://mcp.voidmob.com/mcp as a remote MCP server — streamable HTTP — and sign in with a VoidMob account when prompted. The README lists setup paths for Claude Code, Claude Desktop and claude.ai, ChatGPT in Developer mode, Cursor, VS Code, and Perplexity, with menu names varying by version. There is also a sandbox at https://mcp.voidmob.com/sandbox/ with mock data and a $500 play balance, and a local option via npx -y @voidmob/mcp using an API key in VOIDMOB_API_KEY. For clients without sign-in support, the README notes an Authorization: Bearer vmk_live_... fallback. Permissions are the product, not an afterthought What makes this more than a wrapped API key is how access is split. On connect, an app gets one of three levels: View to look up prices, balance, and orders; Manage to also create deposits, cancel, reuse a number, rotate IPs, and edit proxy lists; or Buy to also make purchases, renewals, and top-ups. Apps VoidMob does not recognize start at View, and the agent only sees the tools its level allows. Spending controls sit server-side. You can set a maximum per order and a daily limit over a rolling 24 hours, net of refunds. Both are off by default, but when set, VoidMob enforces them on every purchase regardless