Bulk Phone Number Validator & Cleaner: Carrier, CSV or Sheet

io.github.Nero-EnginePublished by GitHub account Nero-Enginev0.1.0Updated Oct 25, 2026

Bulk phone validation for an Apify dataset, CSV/Excel/JSON file or Google Sheet

VerifiedStreamable HTTPWeb executableFiles & StorageData & Analytics

Overview

AI-generated overview

An Apify-hosted remote MCP server that lets an assistant bulk-validate and clean phone numbers from a dataset, CSV/Excel/JSON file or Google Sheet.

What you can do
Validate phone numbers in bulk from an Apify dataset, an uploaded CSV, Excel or JSON file, or a Google Sheet, returning cleaned results. Carrier and other number details are indicated by the server name, but no individual tools are listed in the supplied material.
When to use it
Useful when you have a list of phone numbers in a spreadsheet, file or Apify dataset and want an assistant to check and clean them in bulk rather than one at a time.
Requirements
A remote MCP endpoint at mcp.apify.com over streamable HTTP, with OAuth authentication. An Apify API token is required, sent in the Authorization header as a Bearer token. Runs are billed to your Apify account.
Before you install
The Authorization header carries your Apify API token, a secret; keep it private. Runs are billed per event to your Apify account, so bulk jobs can cost money. Phone numbers you submit are sent to Apify's service for processing.

Installation

In SourceWeft

  1. Open Bulk Phone Number Validator & Cleaner: Carrier, CSV or Sheet 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.Nero-Engine%2Fphone-number-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": {
    "bulk-phone-number-validator-cleaner-carr": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=nerolabs/phone-number-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. v0.1.0LatestOct 1, 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.