DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to recover when an SMS code does not arrive with MCP Server

Ask for another SMS or cancel for a refund when a code never lands.

Authorization notice. MCP Server is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forAn agent operator whose verification run stalled because the code did not arrive on the ordered number.

The problemA stalled activation holds the number and the balance, and the agent needs a clean way to retry or stop.

The outcomeEither a second code is delivered on the same number, or the activation is cancelled and the money returned.

What you need first

  • An SV Number account created at https://sms-verification-number.com/en/register/
  • An API key from https://sms-verification-number.com/en/user/profile/
  • A funded account balance, since the README says there is no free tier
  • An MCP-capable agent such as Claude Code, Codex, Cursor or Claude Desktop

Steps

  1. Call wait_for_code on the activationId and check whether the code arrived.
  2. If no code arrived, call request_another_sms on the same activationId.
  3. If the code still does not arrive, call cancel_activation to cancel and get the money back.
  4. Call order_number again with a different country if the retry must use a new number.
  5. Call get_balance to confirm the refund on the account.

Prompt for your agent

Using the sv-number/mcp-server tools, check the activation <activationId> with wait_for_code, then call request_another_sms once if no code arrived, and cancel_activation if it still fails. Expected output: either a parsed code or a cancellation result with the balance from get_balance. Verify that the cancellation result is returned before you report the money as refunded.

Caveat. The README says polling stops at the 20 minute life of a number, so a stalled activation must be handled inside that window.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page