Byteplant Mcp

io.github.byteplant-devPublished by GitHub account byteplant-devv1.0.0Updated Oct 24, 2026

An MCP server that provides Email, Phone and Address Validation Services from Byteplant

VerifiedSTDIODesktop onlyData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Local MCP server that lets an assistant validate email addresses, phone numbers and postal addresses through Byteplant's validation APIs.

What you can do
  • Validate an email address for deliverability and detect freemail providers
  • Validate a phone number and get line type, carrier codes, location and formats
  • Validate and standardize a postal address, with optional geocoding
  • Each tool returns status codes, standardized fields and diagnostic hints, and accepts a timeout parameter
When to use it
Useful when an assistant needs to check contact data before using it: cleaning email lists, confirming whether a number is mobile or landline, or normalizing and geocoding postal addresses during data entry or CRM work.
Requirements
Runs locally over stdio as a PyPI package, launched with uvx or installed with pip; needs Python 3.10 or later. Each tool needs its own Byteplant API key set as an environment variable: EV_TOKEN for email, PV_TOKEN for phone, AV_TOKEN for address. Network access to the Byteplant APIs is required, and the client must support local stdio servers.
Before you install
Three API keys are passed in plain environment variables in client config files, so keep those files private. Validation calls consume your Byteplant account quota and may be rate-limited or rejected when a key is invalid or depleted. Email addresses, phone numbers and postal addresses are sent to Byteplant's servers, so avoid submitting data you are not allowed to share with a third party.

Installation

In SourceWeft

  1. Open Byteplant Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Byteplant]

Byteplant MCP Server

Validate email addresses, phone numbers and postal addresses from any MCP client,
with unparalleled precision in 240+ countries worldwide.

[PyPI version] [License]

Installation · Tools · Credentials · Usage · Compatibility · Resources

This is an MCP server that connects AI assistants such as Claude, Cursor and VS Code to the Byteplant validation APIs. Ask your assistant to check an email address, phone number or postal address, and it calls the matching Byteplant tool and reads back the result.

The server runs locally on your computer and talks to your MCP client over stdio.

Installation

The easiest way to run the server is with uv. uvx downloads the package and a suitable Python version automatically, so there is nothing else to install.

Add the server to your MCP client with one of the configurations below, and replace the placeholders with your API keys. You only need the keys for the services you use.

Claude Desktop

  1. In Claude Desktop, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json:

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
    • Windows: %APPDATA%\Claude\claude_desktop_config.json

  2. Add the Byteplant server:

    json
    {  "mcpServers": {    "byteplant": {      "command": "uvx",      "args": ["byteplant-mcp@latest"],      "env": {        "EV_TOKEN": "<EMAIL VALIDATOR API KEY>",        "PV_TOKEN": "<PHONE VALIDATOR API KEY>",        "AV_TOKEN": "<ADDRESS VALIDATOR API KEY>"      }    }  }}

  3. Restart Claude Desktop.

Claude Code

bash
claude mcp add \  --env EV_TOKEN=<EMAIL VALIDATOR API KEY> \  --env PV_TOKEN=<PHONE VALIDATOR API KEY> \  --env AV_TOKEN=<ADDRESS VALIDATOR API KEY> \  --transport stdio byteplant -- uvx byteplant-mcp@latest

Cursor

Add the same mcpServers entry as for Claude Desktop to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project).

VS Code

Add the server to .vscode/mcp.json in your project:

json
{  "servers": {    "byteplant": {      "type": "stdio",      "command": "uvx",      "args": ["byteplant-mcp@latest"],      "env": {        "EV_TOKEN": "<EMAIL VALIDATOR API KEY>",        "PV_TOKEN": "<PHONE VALIDATOR API KEY>",        "AV_TOKEN": "<ADDRESS VALIDATOR API KEY>"      }    }  }}

Using pip instead of uv

bash
pip install byteplant-mcp

This installs a byteplant-mcp command. Use its full path as the command, because desktop apps often don't see your shell's PATH (find it with which byteplant-mcp on macOS/Linux or where byteplant-mcp on Windows):

json
"command": "/full/path/to/byteplant-mcp"

Alternatively, run the module with the Python installation you installed it into:

json
"command": "/path/to/python","args": ["-m", "byteplant_mcp"]

Tools

ToolWhat it does
validate_emailChecks whether an email address is deliverable and detects freemail providers
validate_phoneValidates a phone number and returns its line type, carrier codes, location and formats
validate_addressValidates and standardizes a postal address, with optional geocoding

Credentials

Each tool uses its own API key, passed to the server as an environment variable. Sign up for the service you need to get one:

Environment variableUsed byGet an API key
EV_TOKENvalidate_emailEmail Validator
PV_TOKENvalidate_phonePhone Validator
AV_TOKENvalidate_addressAddress Validator

You can manage your keys in your Byteplant account. If a key is missing, the matching tool tells the assistant which variable to set instead of calling the API.

Usage

Just ask your assistant in plain language, for example:

  • "Is [email protected] a valid email address?"
  • "Check whether +49 9874 322466 is a mobile or a landline number."
  • "Validate this address and give me the standardized version: Heilsbronner Str. 4, 91564 Neuendettelsau, Germany."

The assistant fills in the tool parameters below. Every tool also has a timeout parameter, which sets how long the API may take to respond: 5–300 seconds, 10 by default.

validate_email - API Docs

ParameterRequiredDescription
email✅The email address to validate
Output
FieldDescription
statusNumeric result code, e.g. 200 for a valid address. See the full list of result codes.
categoryAdded by the server: VALID, SUSPECT, INVALID or INDETERMINATE, based on status (UNKNOWN for unlisted codes)
status_descriptionAdded by the server: what the status code means
infoShort status description
detailsFull status description
freemailtrue if the address belongs to a freemail provider (Gmail, Yahoo, Outlook/Hotmail/Live, AOL, …)

validate_phone - API Docs

ParameterRequiredDescription
phone✅The phone number to validate, in national format or in international format with a leading +
codeTwo-letter ISO 3166-1 country code. Optional if the phone number is in international format.
localeIETF language tag for geocoding results. Defaults to en-US.
modeextensive (default) runs full validation. express runs static checks only and is faster.
Output
FieldDescription
statusVALID_CONFIRMED, VALID_UNCONFIRMED, INVALID, DELAYED, RATE_LIMIT_EXCEEDED or API_KEY_INVALID_OR_DEPLETED
linetypeFIXED_LINE, MOBILE, VOIP, TOLL_FREE, PREMIUM_RATE, SHARED_COST, PERSONAL_NUMBER, PAGER, UAN or VOICEMAIL
locationGeographical location (city, county, state)
countrycodeTwo-letter ISO 3166-1 country code
formatnationalPhone number in national format
formatinternationalPhone number in international format
mccMobile country code, which identifies the mobile network operator (carrier)
mncMobile network code, which identifies the mobile network operator (carrier)

validate_address - API Docs

ParameterRequiredDescription
code✅Two-letter ISO 3166-1 country code. Use XX for international addresses.
street_adr✅Street, house number and building. May include the unit or apartment, or even the complete address.
street_numHouse or building number, if it isn't part of street_adr
additional_infoBuilding, unit, apartment or floor
cityCity or locality
postal_codeZIP or postal code
stateState or province
geocodingWhether to return coordinates for the address. Off by default.
localeOutput language for countries with more than one postal language. Use it only to translate addresses, and leave it empty for address validation.
charsetutf-8 (default) or us-ascii
Output
FieldDescription
statusVALID: the address is correct and deliverable. SUSPECT: the address needs corrections to be deliverable, and a suggested correction is provided. INVALID: the address is not deliverable and can't be corrected automatically. Other values: DELAYED, NO_COUNTRY, RATE_LIMIT_EXCEEDED, API_KEY_INVALID_OR_DEPLETED, RESTRICTED, INTERNAL_ERROR
formattedaddressFull address in standardized format
supplementAdditional address details (building, unit, apartment, suite)
streetStreet in standardized format
streetnumberStreet number in standardized format
postalcodeZIP or postal code in standardized format
cityCity in standardized format
districtDistrict in standardized format
countyCounty in standardized format
stateState or province in standardized format
countryTwo-letter ISO 3166-1 country code
typeAddress type: S for a street address, P for a P.O. box, pick-up or other delivery service
rdiResidential Delivery Indicator: commercial or residential
diagnosticsHints about errors in the address input. See the full list of diagnostic hints.
correctionsHints about which parts of the address input were fixed. See the full list of correction hints.
latitude, longitudeCoordinates. Only returned for valid addresses when geocoding is on.

Compatibility

RequirementVersion
Python3.10 or later (installed automatically by uvx)
MCP clientAny client that runs local stdio servers, e.g. Claude Desktop, Claude Code, Cursor, VS Code, Windsurf or OpenAI Codex

ChatGPT and Claude on the web or mobile only connect to remote (hosted) MCP servers, so they can't use this server yet.

Resources

License

MIT

Source: README.md at commit 023a7f9

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

50% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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
  • License10 pts