io.github.byteplant-devops/byteplant-mcp
PYPI · BYTEPLANT-MCP · 2 COMPONENTS
An MCP server that provides Email, Phone and Address Validation Services from Byteplant
Available components
Last scanned (16 hours ago)
Scores higher than 73% of PyPI servers
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 35 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1304 tokens (~434/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −5
- Stability: pass → 0.67 functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/byteplant-mcp@1.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
validate_address Validate a postal address ~658
Validate and standardize a postal address and return its status, standardized address components, and optionally its coordinates. Result fields: - status (string): VALID: address is correct and deliverable. SUSPECT: address is incorrect and needs corrections to be deliverable, a suggested correction is provided. INVALID: address is incorrect and not deliverable - either there is no match at all in the reference data or the address is ambiguous and there are a lot of different matches. In these cases automatic correction suggestions are not available. DELAYED, NO_COUNTRY, RATE_LIMIT_EXCEEDED, API_KEY_INVALID_OR_DEPLETED, RESTRICTED, INTERNAL_ERROR - formattedaddress (string): full address in standardized format - supplement (string): additional address details (building / unit / apt / suite etc.) - street (string): street address in standardized format - streetnumber (string): street number in standardized format - postalcode (string): zip / postal code in standardized format - city (string): city in standardized format - type (string): address type: S = Street address | P = P.O. Box, Pick-Up or other delivery service - rdi (string): Residential Delivery Indicator (Commercial / Residential) - district (string): district in standardized format - county (string): county in standardized format - state (string): state / province in standardized format - country (string): two-letter ISO 3166-1 country code - latitude (number): latitude (for valid addresses if Geocoding is enabled) - longitude (number): longitude (for valid addresses if Geocoding is enabled) - diagnostics (string): detailed diagnostic hints, indicating errors in the address input - corrections (string): detailed correction hints, indicating which parts of the address input have been fixed - ratelimit_remain (int): number of API requests remaining before the API rate limit is reached (the default API rate limit allows 100 API requests in 300s) - ratelimit_seconds (int): number of seconds remaining…
| Name | Type | Req | Description |
|---|---|---|---|
| additional_info | string | – | Building/unit/apt/floor etc. |
| charset | string | – | Output character set: 'utf-8' or 'us-ascii' |
| city | string | – | – |
| code | string | yes | Two-letter ISO 3166-1 country code, 'XX' for international |
| geocoding | boolean | – | Return latitude and longitude for valid addresses |
| locale | string | – | Output language for countries with multiple postal languages, as an IETF language tag. Use only to translate addresses; always leave empty for address validation |
| postal_code | string | – | – |
| state | string | – | – |
| street_adr | string | yes | Street, house number and building, may include unit/apt etc. May also contain the complete address (leave the other optional fields empty then). Always use ',' to separate address elements where requ… |
| street_num | string | – | House number/building, if it isn't part of street_adr |
| timeout | integer | – | Timeout in seconds (min 5, max 300, default 10) |
Structured output declared, but exposes no named fields.
No examples provided.
validate_email Validate an email address ~246
Validate an email address and return info about it. Result fields: - status (int): API result code. 401, 118 and 119 status codes indicate API errors: 401 -> info: 'Email address missing' 118 -> info: 'Rate Limit Exceeded' 119 -> info: 'API Key Invalid or Depleted' - info (string): short status description - details (string): full status description - freemail (boolean): indicates freemail addresses (Gmail, Yahoo, Outlook/Hotmail/Live, AOL, ...) [true | false] - ratelimit_remain (int): number of API requests remaining before the API rate limit is reached (the default API rate limit allows 100 API requests in 300s) - ratelimit_seconds (int): number of seconds remaining in the current rate limit interval - category, status_description: added from the numeric status code (category is VALID, SUSPECT, INVALID, INDETERMINATE or UNKNOWN)
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address to validate | |
| timeout | integer | – | Timeout in seconds (min 5, max 300) |
Structured output declared, but exposes no named fields.
No examples provided.
validate_phone Validate a phone number ~400
Validate a phone number and return its status, line type, carrier codes, location and national/international formats. Result fields: - status (string): VALID_CONFIRMED, VALID_UNCONFIRMED, INVALID, DELAYED, RATE_LIMIT_EXCEEDED, API_KEY_INVALID_OR_DEPLETED - linetype (string): FIXED_LINE, MOBILE, VOIP, TOLL_FREE, PREMIUM_RATE, SHARED_COST, PERSONAL_NUMBER, PAGER, UAN, VOICEMAIL - location (string): geographical location (city, county, state) - countrycode (string): two letter ISO 3166-1 country code - formatnational (string): phone number in national format - formatinternational (string): phone number in international format - mcc (string): mobile country code to identify a mobile network operator (carrier) using the GSM (including GSM-R), UMTS, and LTE networks - mnc (string): mobile network code to identify a mobile network operator (carrier) using the GSM (including GSM-R), UMTS, and LTE networks - ratelimit_remain (int): number of API requests remaining before the API rate limit is reached (the default API rate limit allows 100 API requests in 300s) - ratelimit_seconds (int): number of seconds remaining in the current rate limit interval
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | Two letter ISO 3166-1 country code. Required for numbers in national format; leave empty if the number starts with '+' |
| locale | string | – | IETF language tag for geocoding results |
| mode | string | – | 'extensive' (full validation) or 'express' (static checks only, faster) |
| phone | string | yes | Phone number to validate, in national format or international format with a leading '+' |
| timeout | integer | – | Timeout in seconds (min 5, max 300) |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.byteplant-devops/byteplant-mcp server?
io.github.byteplant-devops/byteplant-mcp runs locally as a PyPI package, launched with uvx byteplant-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · byteplant-mcp
claude mcp add byteplant-devops-byteplant-mcp -- uvx byteplant-mcp
What is the io.github.byteplant-devops/byteplant-mcp server?
io.github.byteplant-devops/byteplant-mcp is listed in the public MCP registry as io.github.byteplant-devops/byteplant-mcp. An MCP server that provides Email, Phone and Address Validation Services from Byteplant. This page covers its PyPI package (byteplant-mcp).
Is the io.github.byteplant-devops/byteplant-mcp server safe to use?
io.github.byteplant-devops/byteplant-mcp scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.byteplant-devops/byteplant-mcp server expose?
io.github.byteplant-devops/byteplant-mcp exposes 3 tools: validate_email, validate_phone, validate_address. Their descriptions and schemas cost roughly 1,304 tokens of context every time the server is loaded.
Is the io.github.byteplant-devops/byteplant-mcp server still maintained?
io.github.byteplant-devops/byteplant-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.byteplant-devops/byteplant-mcp server under?
io.github.byteplant-devops/byteplant-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.