mcpbeat Sign in

SMS Validator API MCP Server

not responding

SMS Validator API is listed as active in the registry but did not answer our last check. It exposes 1 tools. Last commit 2 Sep 2026.

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

Uptime history 91 days of history · worst day 0%
91 days agonow
0.0%
Uptime 24h
0 of 91 checks
1
Tools
read from the server
8 ms
Response time
average over 24h
0
Stars
last commit 2 Sep 2026

SMS Validator API does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add sms-validator --transport sse https://sms-validator.api.klymax402.com/mcp
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "sms-validator": {
      "type": "sse",
      "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 8 ms 9 min ago

Alternatives to SMS Validator API

same job, measured the same way
X402 Middleware
by gadgethumans-swarm

One-line x402 + Stripe payment middleware for MCP servers. The Stripe for the agent economy.

67 installs/wk local only
Nutriref
by younghef

Pay-per-call USDA nutrition for AI agents (x402 micropayments in USDC on Base).

local only
vn-skills
by beiryu

Vietnam: VietQR, address, tax ID, CCCD, phone, holiday, names, number/date format, lunar, e-invoice

331 installs/wk local only
Clawswap
by wartech9

Cross-chain swaps between Solana and Base for AI agents paid for via via x402 micropayments.

79 installs/wk local only
A
Agentcash
by merit-systems

Generic MCP server for calling x402-protected APIs with automatic payment handling

992 installs/wk local only
MCP Jp Corporate ID
by skypier-jp-works

Validates and normalizes Japanese corporate numbers and invoice registration numbers (format only).

35 installs/wk local only
Solana X402 Compliance
by msantagiulianab

RFC 9110 x402 Solana compliance screening and micropayments gateway for AI agents.

103 installs/wk local only
x711 — Universal Agent Gas Station
by 0580iris-lang

Pay-per-use tool API for AI agents. Free tier, x402 USDC micropayments, or API key.

47 tools answering

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 0 of 91 checks got a reply (0.0%), average response time 8 ms. The bar chart above shows every period we have measured.
The registry lists SMS Validator API as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
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 in the form 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.
Is SMS Validator API open source?
The code is open source: it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at sms-validator.api.klymax402.com, which runs on its operator's own terms.