mcpbeat

SMS Validator API MCP Server

io.github.Br0ski777/sms-validator
answering

SMS Validator API is answering right now. Last checked 2 min ago. It exposes 1 tools. Last commit 19 Jul 2026.

Validate SMS-capable phone numbers — mobile vs landline, E.164 format. x402 micropayment.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
92 of 92 checks
1
Tools
read from the server
31 ms
Response time
average over 24h
0
Stars
last commit 19 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add sms-validator --transport http https://sms-validator.api.klymax402.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "sms-validator": {
      "url": "https://sms-validator.api.klymax402.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.sms-validator]
url = "https://sms-validator.api.klymax402.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "sms-validator": {
      "url": "https://sms-validator.api.klymax402.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "sms-validator": {
      "url": "https://sms-validator.api.klymax402.com/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

sms
sms_validate_number
Use this when you need to check if a phone number can receive SMS messages. Returns SMS capability data in JSON. Returns: 1. canReceiveSMS (boolean) 2. carrierType (mobile/landline/voip) 3. e164 formatted number 4. countryCode 5. numberType (mobile/landline/voip/toll-free) 6. carrier name. Example output: {"phone":"+14155551234","canReceiveSMS":true,"carrierType":"mobile","e164":"+14155551234","countryCode":"US","numberType":"mobile","carrier":"T-Mobile"} Use this BEFORE sending SMS campaigns, FOR filtering landlines from SMS lists, verifying 2FA phone numbers, and OTP delivery validation. Do NOT use for full phone validation with carrier lookup -- use phone_validate_number instead. Do NOT use for email validation -- use email_verify_address instead. Do NOT use for address validation -- use address_validate instead.

Endpoints

URLTransportStateLatencyChecked
https://sms-validator.api.klymax402.com/mcp sse answering 17 ms 2 min ago

SMS Validator API — questions

Answers built from our own checks of this server.

What can SMS Validator API do?
It exposes 1 tools, read directly from the server on our last check. Among them: sms_validate_number. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is SMS Validator API working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 31 ms. The bar chart above shows every period we have measured.
How do I connect SMS Validator API?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does SMS Validator API need an API key?
No. SMS Validator API completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is SMS Validator API?
It answers our handshake in 31 ms on average, which is faster than 99% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is SMS Validator API open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.