Byteplant Validator MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AV_TOKEN | No | Your Address Validator API Token | |
| EV_TOKEN | No | Your Email Validator API Token | |
| PV_TOKEN | No | Your Phone Validator API Token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_emailB | Validate an email address and return info about it. Result fields:
|
| validate_phoneB | Validate a phone number and return its status, line type, carrier codes, location and national/international formats. Result fields:
|
| validate_addressA | Validate and standardize a postal address and return its status, standardized address components, and optionally its coordinates. Result fields:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct data type (email, address, phone) with no overlap in purpose. An agent can easily select the correct tool based on input type.
All tools follow the same predictable verb_noun pattern: validate_email, validate_address, validate_phone. No naming deviations or mixed conventions.
Three tools cleanly cover the three core validation domains. The count is well-scoped with each tool earning its place.
The server provides complete validation coverage for email, postal address, and phone number, which are the primary contact-data validation needs. No obvious missing operations for a read-only validation service.