mcp-server-sv-number

name	mcp-server-sv-number
description	Drive the SV Number MCP server (`sv-number-mcp`), nine stdio tools that order a private phone number for one signup, read the SMS verification code straight from the API, and hand the number back — covering 200+ countries. Use when an agent hits a signup form that needs a real phone number for an OTP/SMS code, when picking a country or service code (`list_countries`, `list_services`), ordering and polling a number (`order_number`, `wait_for_code`), closing out an activation (`finish_activation`, `cancel_activation`, `request_another_sms`), checking account balance (`get_balance`), or computing a TOTP/2FA code locally from a shared secret (`totp_code`). Triggers on: "sv-number", "sv-number-mcp", "SMS verification number", "order a phone number for OTP", "receive SMS verification code", "temporary/virtual number for signup", "sms-verification-number.com", "wait_for_code", "totp_code", "phone number MCP server for agents".
allowed-tools	Bash Read Write Edit Glob Grep
compatibility	Node.js >=18. Runs over stdio via `npx -y sv-number-mcp`; no build step for consumers. Requires a funded `SVN_API_KEY` from sms-verification-number.com — there is no free tier. MIT license; the underlying SMS service is a commercial, paid API.
metadata	{"tags":"mcp, mcp-server, sms, otp, phone-verification, sms-verification, sv-number, ai-agents, stdio, npx, totp","platforms":"Claude, ChatGPT, Gemini, Codex","version":"1.0","source":"https://github.com/sv-number/mcp-server"}

SV Number MCP Server

SV Number is a stdio MCP server that turns phone numbers into tools: an agent orders a private number in the country a service expects, reads the SMS verification code straight from the API, and hands the number back. Nine tools, no SDK to learn, 200+ countries of coverage. It is not a messaging or calling product — receiving one verification code per activation is the whole job.

When to use this skill

• A signup or account-creation flow demands a real phone number to receive an SMS/OTP code
• Picking the right country id and service code before ordering a number (list_countries, list_services)
• Ordering a number, waiting for the code, and closing out the activation (order_number, wait_for_code, finish_activation, cancel_activation)
• Requesting a second SMS on the same number for a resend/password reset (request_another_sms)
• Checking remaining account balance before ordering (get_balance)
• Computing a TOTP/2FA code locally from an already-known Base32 secret (totp_code)
• Wiring this MCP server into Claude Code, Claude Desktop, Codex, or Cursor

When not to use this skill

• The user needs a persistent number for real conversations, calls, banking, payment, or government accounts — these numbers are exclusive to one activation and expire in 20 minutes; point them at a carrier product instead
• No SVN_API_KEY is configured and funding one is out of scope for the task — say so rather than guessing a key
• The task is about sending or receiving arbitrary SMS/voice traffic, not a one-time verification code — out of scope for this server
• A general MCP client setup question unrelated to SV Number specifically → use a generic MCP-configuration skill instead

Instructions

Step 1: Confirm the environment before ordering anything

node --version   # needs >=18
echo "${SVN_API_KEY:+set}"

SVN_API_KEY comes from the user's profile page after signup, and the balance must be funded — there is no free tier. Never print or echo the key itself; the server reads it from the environment and no tool or error message ever returns it.