mcpField
S
Sms Validator X402

Sms Validator X402

Remote
github.comCommunication0Updated 8w ago

About Sms Validator X402

Sms Validator X402 is an MCP server and pay-per-call API for checking whether phone numbers can receive SMS. It returns number format, SMS capability, and carrier-type data for agents and other clients.

Key features

  1. 01Check SMS receiving capability
  2. 02Distinguish mobile and landline numbers
  3. 03Return E.164 format and number type
  4. 04Pay per call with x402

Use cases

  1. 01Filter landlines from SMS campaign lists
  2. 02Check phone numbers for 2FA
  3. 03Validate numbers for OTP delivery

MCP support

The MCP server exposes the sms_validate_number tool for checking SMS capability. It is also available over HTTP with x402 pay-per-call payments.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://sms-validator.api.klymax402.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

SMS Validator API

MCP Server x402 License: MIT

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.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

{
  "mcpServers": {
    "sms-validator": {
      "url": "https://sms-validator.api.klymax402.com/mcp"
    }
  }
}

Quickstart -- HTTP (x402)

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.

Tools

ToolMethodPathPriceDescription
sms_validate_numberPOST/api/validate$0.005Validate if a phone number can receive 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.

Parameters

NameTypeRequiredDescription
phonestringyesPhone number with country code (e.g. +14155551234)
countryCodestringnoISO 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).

Example agent prompts

  • "Check if a phone number can receive SMS messages"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)
  • Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.