Server data from the Official MCP Registry
Validate SMS-capable phone numbers — mobile vs landline, E.164 format. x402 micropayment.
Validate SMS-capable phone numbers — mobile vs landline, E.164 format. x402 micropayment.
Remote endpoints: sse: https://sms-validator.api.klymax402.com/mcp
Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. Trust signals: trusted author (164/169 approved); 6 highly-trusted packages.
1 tool verified · Open access · No issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"io-github-br0ski777-sms-validator": {
"url": "https://sms-validator.api.klymax402.com/mcp"
}
}
}From the project's GitHub README.
Validate SMS-capable phone numbers -- mobile vs landline detection, carrier type, E.164 format, SMS readiness. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
{
"mcpServers": {
"sms-validator": {
"url": "https://sms-validator.api.klymax402.com/mcp"
}
}
}
curl -X POST "https://sms-validator.api.klymax402.com/api/validate" \
-H "Content-Type: application/json" \
-d '{"phone":"..."}'
# -> 402 Payment Required, with an x402 payment challenge in the response body
Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
sms_validate_number | POST | /api/validate | $0.002 | Validate if a phone number can receive SMS |
sms_validate_numberUse this when you need to check if a phone number can receive SMS messages. Returns SMS capability data in JSON.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
phone | string | yes | Phone number with country code (e.g. +14155551234) |
countryCode | string | no | ISO 3166-1 alpha-2 country code hint (e.g. US, FR, GB) |
Example response:
{"phone":"+14155551234","canReceiveSMS":true,"carrierType":"mobile","e164":"+14155551234","countryCode":"US","numberType":"mobile","carrier":"T-Mobile"}
When to use: sending SMS campaigns, FOR filtering landlines from SMS lists, verifying 2FA phone numbers, and OTP delivery validation.
Not for: full phone validation with carrier lookup (use phone_validate_number), email validation (use email_verify_address), address validation (use address_validate).
eip155:8453)100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
MIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
by Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption
by mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
by mcp-marketplace · Finance
Free stock data and market news for any MCP-compatible AI assistant.