Phone Number Validator: E.164, country and line type, offline

io.github.bepolabsPublished by GitHub account bepolabsv1.0.0Updated Nov 12, 2026

E.164, country and line type, offline, as one MCP tool through Apify

The publisher's own server: type.com

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

An Apify-hosted MCP tool that validates phone numbers offline, returning E.164 format, country and line type.

What you can do
  • Validate a phone number and get its normalized E.164 form
  • Identify the country associated with a number
  • Report the line type of a number
  • Runs offline, without external lookups per the description
When to use it
Useful when an assistant needs to check or normalize phone numbers, for example cleaning contact data or confirming a number's country and line type before storing it.
Requirements
Remote MCP endpoint at mcp.apify.com over streamable HTTP. Authentication is required: either an Apify API token sent as an Authorization Bearer header or sign-in through OAuth.
Before you install
Requires an Apify account credential (API token or OAuth sign-in) that grants access to the Apify platform; keep the token private. Phone numbers submitted are handled by the Apify-hosted service.

Installation

In SourceWeft

  1. Open Phone Number Validator: E.164, country and line type, offline in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/io.github.bepolabs%2Fphone-validator/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "phone-number-validator-e-164-country-and": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=bepolabs/phone-validator"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 12, 2026

Score

67% 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 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

    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.

Other Type integrations