Phone Number Validation API

io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Oct 24, 2026

Validate phone numbers worldwide: carrier, line type, country, E.164. x402.

VerifiedSSEWeb executableFinanceCommunication & Collaboration

Overview

AI-generated overview

Remote MCP server that validates phone numbers worldwide, returning carrier, line type, country and E.164 format, paid per call via x402.

What you can do
Validate a single phone number and get carrier, line type, country and E.164 formatting in JSON, with local and international formats returned too. Validate a batch of up to 50 numbers at once and get an array of results with a total and valid count. Intended for CRM cleaning, lead validation, fraud detection and KYC phone checks.
When to use it
Useful when an assistant needs to check whether phone numbers are valid and learn their carrier, line type or country, for example cleaning a contact list, validating leads, or verifying numbers before SMS or calls.
Requirements
A remote MCP endpoint reached over SSE; no API key or signup. Payment is per call in USDC on Base L2 through the x402 protocol, so an x402-aware client with a funded wallet is needed to complete the 402 challenge and retry.
Before you install
Every call costs money: $0.008 per single validation and $0.035 per batch, paid in USDC on Base, so an assistant could spend funds without a clear limit. Phone numbers are sent to a third-party service for validation. The README also points to other klymax402 APIs and a shared wallet setup.

Installation

In SourceWeft

  1. Open Phone Number Validation 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%2Fphone-validation/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": {
    "phone-number-validation-api": {
      "type": "sse",
      "url": "https://phone-validation.api.klymax402.com/mcp"
    }
  }
}

README

Phone Number Validation API

[MCP Server] [x402] [License: MIT]

Validate phone numbers worldwide -- carrier, line type, country, E.164 format. Single and batch (50) modes. 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": {    "phone-validation": {      "url": "https://phone-validation.api.klymax402.com/mcp"    }  }}

Quickstart -- HTTP (x402)

bash
curl "https://phone-validation.api.klymax402.com/api/validate?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
phone_validate_numberGET/api/validate$0.008Validate a phone number and get carrier/type/country info
phone_validate_batchPOST/api/validate/batch$0.035Validate up to 50 phone numbers in a single batch request

phone_validate_number

Use this when you need to validate a phone number and get carrier info. Returns structured validation data in JSON.

Parameters

NameTypeRequiredDescription
phonestringyesPhone number to validate (e.g. +33612345678, +14155552671, 0033612345678)

Example response:

json
{"valid":true,"e164":"+33612345678","countryCode":"FR","countryName":"France","carrier":"Orange","lineType":"mobile","localFormat":"06 12 34 56 78","internationalFormat":"+33 6 12 34 56 78"}

When to use: sending SMS or calling a number, FOR CRM data cleaning, lead validation, fraud detection, and KYC phone verification.

Not for: SMS capability check (use sms_validate_number), email validation (use email_verify_address), person data (use person_enrich_from_email).

phone_validate_batch

Use this when you need to validate multiple phone numbers at once (up to 50). Returns an array of validation results in JSON.

Parameters

NameTypeRequiredDescription
phonesarrayyesArray of phone numbers to validate (max 50)

Example response:

json
{"results":[{"phone":"+14155551234","valid":true,"e164":"+14155551234","countryCode":"US","carrier":"T-Mobile","lineType":"mobile"},{"phone":"invalid","valid":false}],"total":2,"validCount":1}

When to use: bulk CRM cleaning, importing contact lists, deduplication pipelines, and batch lead validation.

Not for: single numbers (use phone_validate_number), SMS capability (use sms_validate_number).

Example agent prompts

  • "Validate a phone number and get carrier info"
  • "Validate multiple phone numbers at once (up to 50)"

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 22ced33

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