Every call costs real balance, so the ordering is deliberate: check the price and availability for a country and service, then order, then poll. Numbers and services are addressed by name rather than by catalog ID, and an activation that never receives its SMS can be cancelled to get the reserved funds back.
A server over the Platfone API for temporary phone numbers. It runs the full activation lifecycle: price a country and service, order a number, poll for the SMS, then retry or cancel.
- Pricing before you commit — minimum, maximum and suggested price, an average quality score, and how many numbers are available for that country and service
- A rented number returned with its activation ID, resolved country and service names, price, expiry, and whether it can be retried or cancelled
- Country and service given as ordinary names — 'Israel', 'Telegram' — resolved server-side, so the agent never receives the whole catalog
- Activation state on demand or by polling: the SMS text, the parsed code, status and expiry
- A second SMS on the same number at no charge, once the first has been received
- Cancellation that releases the number and the funds it reserved, allowed while the activation is still waiting on its first SMS
- Account balance split into total funds and the amount reserved by active orders, in USD cents
A Platfone account with funds, and an API key from https://platfone.com/app/api. Two transports from the same build: stdio via npx @platfone/mcp with PLATFONE_API_KEY set, or the hosted streamable-http endpoint https://mcp.platfone.com/mcp, where the key can travel in an x-api-key header instead. The published npm package is @platfone/mcp, currently 1.1.8. PLATFONE_API_URL overrides the API base — it is what points the server at the sandbox. Building from source needs Node.js 18 or newer.
One command plus a key — PLATFONE_API_KEY=your_key npx @platfone/mcp, then supply credentials