What it does
The server checks phone numbers from any country and returns structured JSON with carrier, line type, country and E.164 format. It exposes two tools: a single-number check at $0.008 per call, and a batch check of up to 50 numbers at $0.035 per call.
The single-number tool fits cases such as confirming a number before sending an SMS or placing a call, cleaning CRM records, validating leads, fraud screening and KYC phone verification. The batch tool fits bulk CRM cleaning, importing contact lists, deduplication pipelines and validating leads in groups. It does not check whether a number can receive SMS, validate email addresses or return person data; the publisher directs those tasks to separate tools.
There is no API key or signup. Each call is paid through the x402 protocol in USDC on Base L2, and x402-aware clients handle the payment challenge and retry automatically. Payments are settled via Coinbase CDP, with PayAI as fallback. The API is also reachable through ATXP. The publisher lists it as part of a marketplace of 100 x402 APIs that share one wallet.
Limitations and requirements
Each call must be paid in USDC on Base L2 through an x402-capable client or wallet. The batch tool accepts at most 50 numbers per request. The single-number tool does not check SMS capability, and the publisher directs that check to a different tool.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
Phone Number Validation API
Validate phone numbers worldwide: carrier, line type, country, E.164. x402.
v1.1.0As shown on registry.modelcontextprotocol.io when we last read it