Potencialize seu agente
O comando do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
uvx byteplant-mcp==1.1.0O Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.
EV_TOKEN=<secret> AV_TOKEN=<secret> PV_TOKEN=<secret> claude mcp add io.github.byteplant-devops-byteplant-mcp -- uvx byteplant-mcp==1.1.0Execute em um terminal.
{ "mcpServers": { "io.github.byteplant-devops-byteplant-mcp": { "command": "uvx", "args": [ "byteplant-mcp==1.1.0" ], "env": { "EV_TOKEN": "<secret>", "AV_TOKEN": "<secret>", "PV_TOKEN": "<secret>" } } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
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.
An MCP server that provides Email, Phone and Address Validation Services from Byteplant
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.
In Claude Desktop, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonAdd the Byteplant server:
{
"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>"
}
}
}
}
Restart Claude Desktop.
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
Add the same mcpServers entry as for Claude Desktop to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project).
Add the server to .vscode/mcp.json in your project:
{
"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>"
}
}
}
}
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):
"command": "/full/path/to/byteplant-mcp"
Alternatively, run the module with the Python installation you installed it into:
"command": "/path/to/python",
"args": ["-m", "byteplant_mcp"]
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:
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.
Just ask your assistant in plain language, for example:
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 Docsvalidate_phone - API Docsvalidate_address - API DocsChatGPT and Claude on the web or mobile only connect to remote (hosted) MCP servers, so they can't use this server yet.
An MCP server that provides Email, Phone and Address Validation Services from Byteplant
{ "mcpServers": { "io.github.byteplant-devops-byteplant-mcp": { "command": "uvx", "args": [ "byteplant-mcp==1.1.0" ], "env": { "EV_TOKEN": "<secret>", "AV_TOKEN": "<secret>", "PV_TOKEN": "<secret>" } } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
O publicador lista estas variáveis de ambiente: EV_TOKEN, AV_TOKEN, PV_TOKEN.
Byteplant roda localmente via stdio.
Última verificação: 2026-11-09. An MCP server that provides Email, Phone and Address Validation Services from Byteplant
