The sandbox is what makes this approachable: one environment variable and all 28 tools run against fake data with a play balance, so the buying path can be walked end to end and reset by restarting.
An MCP server for VoidMob. It covers four product lines — SMS verification rentals, dedicated numbers, mobile proxies and eSIMs — from search and purchase through renewal, rotation and cancellation, plus an account call for balance and rate limits.
- SMS services searched with prices, a US number rented, and its received messages read
- Verification rentals cancelled, reused, extended, or set to auto-renew
- Dedicated numbers searched by country and purchased
- Mobile proxies searched, purchased, renewed, topped up and given a fresh IP
- Proxy passwords regenerated, and proxy lists created, listed and deleted
- eSIM plans searched and purchased, with QR code, status and top-ups
- Balance, rate limits and account ID in one call
- A sandbox mode running every tool against mock data
An API key from the VoidMob dashboard, prefixed vmk_live_ and passed as VOIDMOB_API_KEY, run through npx as @voidmob/mcp. A sandbox switch in the environment boots in-memory mocks with a play-money balance, and state resets on restart.
One command plus a key — npx -y @voidmob/mcp, then supply credentials