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 operations analyst or agent builder who must choose a country and service for a verification workflow and wants evidence first.
The problemPrices and availability differ by country and service, and a wrong choice wastes balance or stalls the workflow.
The outcomeA short comparison showing the country list size, the matched service, its price, its online pool and its deliveredPercent where available.
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
- Add the server to your agent with the JSON config that uses
npx -y sv-number-mcpand your SVN_API_KEY. - Call list_countries and count the rows to check the coverage claim.
- Call list_services with the site name, for example discord.com, and read the matches.
- Compare deliveredPercent for each country. Where it is null, use online as the next signal.
- Call get_balance to confirm the funds cover the planned orders.
Prompt for your agent
Using the sv-number/mcp-server tools, call list_countries and report the number of rows, then call list_services for <site name> 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.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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