This tool validates phone numbers to determine if they're SMS-capable by distinguishing mobile lines from landlines and checking E.164 format compliance. It runs as a remote MCP server over SSE and operates on a micropayment model through the x402 protocol, meaning you pay per validation request. Reach for this when you're building messaging systems that need to verify numbers before attempting delivery, or when you want to filter contact lists to mobile-only numbers. The repository is light on documentation, but the core value is straightforward: ask if a number can receive texts, get a definitive answer, and pay only for what you query.
Public tool metadata for what this MCP can expose to an agent.
sms_validate_numberUse 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 form2 paramsUse 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 form
phonestringcountryCodestringValidate 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
io.github.mindstone/mcp-server-microsoft-teams
com.mintmcp/outlook-email
helbertparanhos/resend-email-mcp
marlinjai/email-mcp
io.github.mindstone/mcp-server-email-imap
io.github.osamahassouna/email-playbook-mcp