Testing anything with phone verification means a human sitting there reading a text message. A blocking wait for the arriving code closes that loop, which is genuinely useful for testing your own flows — and is the same capability someone would want for creating accounts in bulk, so how you use it matters. Using your own handset instead of a carrier API keeps the per-message cost at whatever your plan charges, which for testing volumes is usually nothing.
An SMS gateway that uses a phone you already own as the sending device, exposed so an agent can send messages, issue and verify one-time codes, and react to inbound ones.
- Sending SMS
- Issuing and verifying one-time passcodes
- Waiting for an incoming code, rather than polling for it
- Configuring webhooks for inbound messages
A paired Android phone acting as the gateway, and npx. There is a hosted server too. MIT licensed.
One command plus a key — npx -y sms8-mcp, then supply credentials