Sms Florin Mcp

io.github.flovoice53-techPublished by GitHub account flovoice53-techv0.1.2Updated Nov 5, 2026

Rent a real UK phone number and receive SMS/OTP codes — built for AI coding agents.

The publisher's own server: receivemail.dev

Overview

AI-generated overview

Lets an AI agent rent a real UK phone number and receive SMS/OTP codes inside its workflow, via the sms-florin service.

What you can do
  • List available services (WhatsApp, Telegram, Google, Discord and others) with their prices
  • Rent a number for a service on an instant or monthly basis, returning a rental ID
  • Check a rental's status, phone number and any SMS received so far
  • Wait for the first SMS/OTP to arrive or time out, so an agent can grab a code in one step
When to use it
Useful when an agent is testing a signup or verification flow and needs a real SMS code rather than a mocked one, or when a workflow needs a UK number to receive OTPs.
Requirements
Runs locally over stdio, typically launched with npx, so Node.js is needed. Requires an sms-florin API key supplied in the SMS_FLORIN_API_KEY environment variable; the key is obtained from the provider's site and shares the balance of the regular account. Network access to the sms-florin service is required.
Before you install
Renting a number debits a prepaid balance, so agent calls can spend money. The API key is a secret passed via SMS_FLORIN_API_KEY and should not be exposed in shared configs or logs. The agent can rent numbers and receive verification codes for third-party services, which may conflict with those services' terms; review before letting an agent act unattended.

Installation

In SourceWeft

  1. Open Sms Florin Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

sms-florin-mcp

[npm version] [npm downloads]

[SMS Florin MCP server]

MCP server for sms-florin — lets AI coding agents (Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline...) rent a real UK phone number and receive an SMS/OTP verification code directly inside an agentic workflow. Useful when an agent is testing a signup/verification flow and needs a real code instead of a mocked one.

Numbers are real SIM cards on UK mobile networks — not VoIP — via sms-florin's own GOIP hardware.

Setup

Get an API key at flo-voice1.com/api-access (balance is shared with your regular account).

Claude Code / Claude Desktop

bash
claude mcp add sms-florin -e SMS_FLORIN_API_KEY=your_key_here -- npx -y sms-florin-mcp

Or in claude_desktop_config.json:

json
{  "mcpServers": {    "sms-florin": {      "command": "npx",      "args": ["-y", "sms-florin-mcp"],      "env": { "SMS_FLORIN_API_KEY": "your_key_here" }    }  }}

Cursor / Windsurf / other MCP clients

Same shape — point the client's MCP config at npx -y sms-florin-mcp with SMS_FLORIN_API_KEY set in the env.

Tools

ToolDescription
list_servicesList available services (WhatsApp, Telegram, Google, Discord...) and their prices.
rent_numberRent a number for a service (instant or monthly), debiting your balance. Returns a rentalId.
get_rentalCheck a rental's status, phone number, and any SMS received so far.
wait_for_smsBlock until the first SMS/OTP arrives, or time out — the one-step way to get a code in an automated flow.

Example flow

Rent a WhatsApp number and wait for the verification code.

The agent calls rent_number({ serviceSlug: "whatsapp" }), then wait_for_sms({ rentalId }), and gets the code back to type into the signup form it's testing.

Need one for your own API?

I build custom MCP servers like this one — npm package, published to the official Anthropic MCP registry / Docker MCP catalog / Glama, same setup as above. Details on Fiverr, starting at $90.

License

MIT

Source: README.md at commit 21b5416

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Receivemail integrations