Remote MCP server that validates and formats phone numbers offline, returning E.164, region, calling code and line type.
What you can do
Validate and format a single phone number offline against libphonenumber metadata, returning E.164, international, national and RFC 3966 formats, region, calling code and line type.
Fetch the libphonenumber example mobile number for a region in all formats, for format testing.
When to use it
Useful when an assistant needs to check that a phone number is plausible and well-formed, normalize it to E.164, or get sample numbers for testing input formats. Not suitable when you need to know whether a line is reachable or which carrier it belongs to.
Requirements
A remote streamable HTTP endpoint; nothing to install locally. An Authorization header with a bearer key is optional and only raises rate limits; it works without a key.
Before you install
Validation only confirms the number fits an allocated range, not that the line is connected or reachable, and no carrier lookup is performed. The optional Authorization key is a secret and should not be shared; example numbers are for format testing only and should not be dialed.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. 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/dev.workers.mike-tusa.phonecheck%2Fphonecheck/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.
Validate one phone number offline against libphonenumber metadata and return E.164, international, national and RFC 3966 formats, region, calling code and line type (from the original allocation). Valid means the number fits an allocated range, not that the line is connected or reachable; no carrier/HLR lookup. Read-only. Same engine, keys and limits as POST /v1/parse.
Parametersnumberrequireddefault_country
get_example_number
Get an example number for a region
Return the libphonenumber example (mobile) number for a region, in all formats, for format testing only (do not dial). Read-only. Same data and limits as GET /v1/example/{country}.
Parameterscountryrequired
Version history
1
v0.2.1LatestOct 12, 2026
Score
72%
72% 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
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.