# AI use cases for MCP Server (sv-number/mcp-server) Repo: [sv-number/mcp-server](https://github.com/sv-number/mcp-server) | Use cases: 4 | Page: https://dedupedai.com/use-cases/sv-number-mcp-server/ An MCP server that gives AI agents tools to order a private phone number in a chosen country, read the SMS verification code from it, and hand the number back. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Get an SMS verification code for an agent signup: https://dedupedai.com/use-cases/sv-number-mcp-server/get-sms-code-for-agent-signup/ - Compare country coverage and delivery rates before ordering: https://dedupedai.com/use-cases/sv-number-mcp-server/compare-countries-and-delivery-before-ordering/ - Recover when an SMS code does not arrive: https://dedupedai.com/use-cases/sv-number-mcp-server/recover-when-sms-code-does-not-arrive/ - Generate an authenticator code locally for your own account: https://dedupedai.com/use-cases/sv-number-mcp-server/generate-authenticator-code-locally/ ## How to get an SMS verification code for an agent signup with MCP Server Repo: [sv-number/mcp-server](https://github.com/sv-number/mcp-server) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Let an agent order a number, read the SMS code and close the activation in one run. **Who it is for:** A developer building an agent workflow that must pass phone verification on a service the developer is permitted to use, in a country that service expects. **The problem:** The agent needs a phone number that can receive the verification SMS, and it needs the code back in a form it can enter. **The outcome:** The agent returns the parsed verification code and the activation is closed with finish_activation. ### Steps 1. Create an account, fund the balance, and copy your API key from your profile. 2. Run `claude mcp add sv-number --env SVN_API_KEY=your_key_here -- npx -y sv-number-mcp` or add the JSON config to your agent. 3. Call list_services with the site name or domain and pick the best match. 4. Call order_number with the service code and a country id, then call wait_for_code with the activationId. 5. Call finish_activation once the code has been used. ### Prompt to paste into your agent ```text Using the sv-number/mcp-server MCP tools, order a number for service in country , then call wait_for_code on its activationId. Expected output: the verification code as returned by wait_for_code, followed by a finish_activation result. Verify that the code is parsed text and not a raw SMS body before you use it. ``` ### Caveat These numbers only receive codes: they do not send SMS or take calls, and the README says they are not meant for banking, payment or government accounts. Risk, credentials: The verification code grants account access, so the agent must only use it on accounts the operator is authorized to create or access. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/sv-number-mcp-server/get-sms-code-for-agent-signup/ ## How to compare country coverage and delivery rates before ordering with MCP Server Repo: [sv-number/mcp-server](https://github.com/sv-number/mcp-server) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Check how many countries and how many live numbers exist before spending balance. **Who it is for:** An operations analyst or agent builder who must choose a country and service for a verification workflow and wants evidence first. **The problem:** Prices and availability differ by country and service, and a wrong choice wastes balance or stalls the workflow. **The outcome:** A short comparison showing the country list size, the matched service, its price, its online pool and its deliveredPercent where available. ### Steps 1. Add the server to your agent with the JSON config that uses `npx -y sv-number-mcp` and your SVN_API_KEY. 2. Call list_countries and count the rows to check the coverage claim. 3. Call list_services with the site name, for example discord.com, and read the matches. 4. Compare deliveredPercent for each country. Where it is null, use online as the next signal. 5. Call get_balance to confirm the funds cover the planned orders. ### Prompt to paste into your agent ```text Using the sv-number/mcp-server tools, call list_countries and report the number of rows, then call list_services for and compare deliveredPercent and online across the top matches. Expected output: a table of country and service options with price, online and deliveredPercent. Verify that every figure comes from a tool response and not from memory. ``` ### Caveat The README says the catalogue is not the same in every country, so a service missing in one country may still be available in another. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/sv-number-mcp-server/compare-countries-and-delivery-before-ordering/ ## How to recover when an SMS code does not arrive with MCP Server Repo: [sv-number/mcp-server](https://github.com/sv-number/mcp-server) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Ask for another SMS or cancel for a refund when a code never lands. **Who it is for:** An agent operator whose verification run stalled because the code did not arrive on the ordered number. **The problem:** A stalled activation holds the number and the balance, and the agent needs a clean way to retry or stop. **The outcome:** Either a second code is delivered on the same number, or the activation is cancelled and the money returned. ### 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 to paste into your agent ```text Using the sv-number/mcp-server tools, check the activation 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. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/sv-number-mcp-server/recover-when-sms-code-does-not-arrive/ ## How to generate an authenticator code locally for your own account with MCP Server Repo: [sv-number/mcp-server](https://github.com/sv-number/mcp-server) | Difficulty: Advanced | Time: 30 minutes | Basis: From the README Compute a time-based one-time code on your machine using the totp_code tool. **Who it is for:** A developer whose agent must log into an account the developer owns and that asks for an authenticator code. **The problem:** The agent needs the current six-digit style time-based code and must compute it without sending the secret elsewhere. **The outcome:** The agent receives an authenticator code computed locally by RFC 6238. ### Steps 1. Add the server with `claude mcp add sv-number --env SVN_API_KEY=your_key_here -- npx -y sv-number-mcp`. 2. Store the authenticator secret for your own account in a location the agent can read, and keep it out of logs. (inferred, check the README) 3. Call totp_code with that secret to get the current code. 4. Enter the code into the login flow within its validity window. ### Prompt to paste into your agent ```text Using the sv-number/mcp-server totp_code tool, compute the current authenticator code for from its secret. Expected output: the current time-based code computed locally by RFC 6238. Verify that the secret is not echoed in the response or in any log before you use the code. ``` ### Caveat The README describes totp_code as local computation, but it does not describe how the secret should be supplied, so check the tool schema before storing any secret. Risk, credentials: The authenticator secret grants access to the account, so it must belong to an account the operator controls and must be stored securely. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/sv-number-mcp-server/generate-authenticator-code-locally/