SMS Validator API

io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Nov 2, 2026

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

VerifiedSSEWeb executableFinanceCommunication & Collaboration

Overview

AI-generated overview

Remote MCP endpoint that checks whether a phone number can receive SMS, returning mobile vs landline type, carrier and E.164 format, paid per call.

What you can do
  • Validate a phone number for SMS capability, returning JSON with canReceiveSMS, number type, carrier type, carrier, E.164 form and country code
  • Accept an optional ISO 3166-1 alpha-2 country code hint alongside the number
  • Settle each call through an x402 micropayment challenge rather than an API key
When to use it
Useful when an assistant needs to screen phone lists before SMS campaigns, filter out landlines, or check that a number is likely to receive 2FA or OTP messages. It is a single-purpose lookup, not a general phone, email or address validation service.
Requirements
A remote MCP client pointed at the hosted endpoint; no local runtime, signup or API key. Calls are paid per use in USDC on Base L2 through the x402 protocol, so an x402-capable client and a funded wallet are needed to complete the payment-and-retry cycle.
Before you install
Each validation costs $0.005 in USDC on Base, so an assistant that calls it repeatedly spends real funds from the connected wallet. Phone numbers are sent to a third-party hosted service and its payment facilitators. The README notes it is not a full carrier-lookup validator and points to other paid APIs for that.

Installation

In SourceWeft

  1. Open SMS Validator API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Br0ski777%2Fsms-validator/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

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.):

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

Quickstart -- HTTP (x402)

bash
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:

json
{"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

Source: README.md at commit 3768f46

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts