A
licenseNot graded
qualityC
maintenanceEnables validating and enriching phone numbers, returning validity, international/national formats, carrier, line type, and country/location data.
115 npm
MIT
Phone Format Check
Server Details
Offline phone number validation and formatting at the edge: E.164/national/international formats,...
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
B3.2/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of confusion between tools. The description clearly defines its purpose, so an agent will know exactly what it does.
Naming Consistency4/5
The single tool name 'run' is generic and does not follow the descriptive verb_noun convention, but since there is only one tool, there are no inconsistencies or mixed patterns to penalize. It earns a slightly reduced score for not conveying the domain.
Tool Count2/5
A single tool is too few for a server that handles validation, multiple formatting standards (E.164/national/international), line type detection, and possibility checks. These are distinct concerns that would be better served by separate tools, making the set feel under-scoped.
Completeness4/5
The single tool appears to cover all the stated operations within its narrow domain, including formatting and line type checks. Minor gaps exist, such as lacking options to request only a specific format or filter results, but the core functionality is present.
Available Tools
1 toolrunCInspect
Offline phone number validation and formatting at the edge: E.164/national/international formats, line type, and possibility checks against real dialing-plan metadata — no per-lookup network call.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| input | Yes |
TDQS
C2.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses useful behavior: it runs offline and makes no per-lookup network call. Since there are no annotations, it carries the full burden, but it does not explain output shape, error behavior, or whether any state is changed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single dense sentence with the main purpose front-loaded and the key detail about no network call placed at the end. There is no wasted prose, though 'possibility checks' remains somewhat underspecified.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, no annotations, and an opaque nested input, the description must supply enough context to invoke the tool correctly. It covers purpose and offline behavior but omits the actual input contract and return format, making it incomplete for reliable use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema only provides an opaque nested input object with 0% description coverage. The description implies that a phone number is involved but does not specify the required input fields, value format, or how multiple numbers are represented, leaving the agent to guess the call contract.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly names the resource (phone numbers) and the specific operations: E.164/national/international formatting, line type, and possibility checks. It does not use a strong imperative verb, but the domain and scope are unmistakable.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It implies when to use the tool: offline or at the edge, when a per-lookup network call is undesirable. However, it does not explicitly state when not to use it or name any alternative tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
run
Related MCP Connectors
Phone carrier lookup, append, verification, DNC, and fraud data services.
Is a phone number VoIP or a real carrier line? Line type, score and grade, free, no auth.
- SnipgetOAuthai.snipget
300+ deterministic data utilities for AI agents: validate, normalize, parse, match, redact.
Fast email validation at the edge: syntax, MX records, disposable-domain detection.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceValidates phone numbers and provides country calling codes, enabling AI agents to look up international dialing codes and filter by country name, ISO code, or calling code.4 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables validating phone numbers and retrieving carrier, line type, country, and location details, as well as listing supported countries and dialing prefixes.MIT
- AlicenseNot gradedqualityCmaintenanceValidates phone numbers worldwide (carrier, line type, country) via single or batch requests, with pay-per-call using x402 micropayments (USDC on Base) — no API key required.MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.