Back to Browse

Phone Validation X402 MCP Server

Developer ToolsModerate5.0MCP RegistryLocalRemote
Free

Server data from the Official MCP Registry

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

About

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

Remote endpoints: sse: https://phone-validation.api.klymax402.com/mcp

Security Report

5.0
Moderate5.0Moderate Risk

This phone validation MCP server is well-structured with appropriate authentication via x402/ATXP payment protocols and reasonable permissions scoped to its purpose. The code is clean and input validation is solid. However, there are minor concerns around error handling, logging practices, and dependency trust that prevent a higher score. Supply chain analysis found 5 known vulnerabilities in dependencies.

5 files analyzed · 14 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

system_info

Check that this permission is expected for this type of plugin.

How to Install & Connect

Available as Local & Remote

This plugin can run on your machine or connect to a hosted endpoint. during install.

Documentation

View on GitHub

From the project's GitHub 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.):

{
  "mcpServers": {
    "phone-validation": {
      "url": "https://phone-validation.api.klymax402.com/mcp"
    }
  }
}

Quickstart -- HTTP (x402)

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:

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

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

Reviews

No reviews yet

Be the first to review this server!