Validate phone numbers for SMS capability, distinguishing mobile from landline and formatting to E.164 standard. Built for developers integrating SMS delivery, verification flows, or contact validation into applications.
io.github.Br0ski777/sms-validator
https://sms-validator-x402-production.up.railway.app/mcp
SSE
No auth required
How models use it and what it is built for.
Validate phone numbers for SMS capability, distinguishing mobile from landline and formatting to E.164 standard. Built for developers integrating SMS delivery, verification flows, or contact validation into applications.
Hosted endpoint — paste into any MCP client.
Where to find authoritative docs and source for SMS Validator API.
Paste any of these into Agent Studio after connecting SMS Validator API.
Common questions about connecting and running SMS Validator API.
What's the difference between mobile and landline validation?
This server identifies whether a phone number is registered to a mobile device (SMS-capable) or a landline (typically not SMS-capable). This matters for SMS delivery—landlines will fail. The server returns the classification so you can route accordingly.
What is E.164 format and why does it matter?
E.164 is the international standard for phone numbers (e.g., +1234567890). Normalizing to E.164 ensures consistency across systems and prevents delivery failures caused by formatting variations like parentheses or dashes.
How does the x402 micropayment model work?
This server uses x402 micropayments, meaning each validation request incurs a small fee. You'll need to set up a payment mechanism compatible with the x402 protocol before making calls. Check the hosted endpoint documentation for payment setup details.
Can I validate numbers from outside the US?
Yes—the server supports international numbers and normalizes them to E.164 format, which includes country codes. This makes it suitable for global SMS validation workflows.
What happens if I validate a number that isn't SMS-capable?
The server will return a classification indicating the number is a landline or non-SMS device. Your application can then decide whether to reject the number, prompt the user for an alternative, or skip SMS delivery for that contact.
Connect SMS Validator API to Claude, GPT, Gemini, DeepSeek and 30+ AI models in MCP Agent Studio. Compare answers side-by-side, save reusable agent presets, share runs — all in your browser, no install required.
Open Agent Studio