Your agent is testing a signup flow and hits "enter the code we texted you". With the sms-florin MCP server it rents a real UK SIM number, waits for the SMS and continues, with no human copying codes between tabs.
Create an API key on the API access page (free account, pay-as-you-go balance), then for Claude Code:
claude mcp add sms-florin -e SMS_FLORIN_API_KEY=your_key_here -- npx -y sms-florin-mcp
Claude Desktop, Cursor, Windsurf, Cline and Codex use the same shape in their MCP config:
{
"mcpServers": {
"sms-florin": {
"command": "npx",
"args": ["-y", "sms-florin-mcp"],
"env": { "SMS_FLORIN_API_KEY": "your_key_here" }
}
}
}list_services
Services and prices available right now.
rent_number
Rent a number for a service (instant or monthly). Debits your balance, returns a rentalId.
get_rental
Status, phone number and any SMS received so far.
wait_for_sms
Blocks until the first code arrives or times out. The one-step way to get an OTP in an automated run.
Prefer plain HTTP? The REST API, the JS/TS SDK and the MCP package all use the same balance.
Testing signup and verification flows that you own or are allowed to test: QA, CI runs, staging environments, agent evals. It is not meant for creating accounts on services in violation of their terms.
No. They are physical SIM cards on a UK mobile network (EE) in our own hardware, which is why they work with flows that reject VoIP numbers.
Instant rentals that expire without receiving an SMS are refunded to your balance automatically, with no support ticket.
An API key can only spend what is on your balance, so keep a small top-up on the account the key belongs to. Each rental is a few cents to a couple of euros; the balance is the hard cap.
Yes. HMAC-signed webhooks push the SMS to your endpoint as soon as it arrives.