io.github.byteplant-dev/byteplant-mcp vs io.github.codespar/mcp-bigdatacorp
io.github.byteplant-dev/byteplant-mcp is an MCP server published by byteplant-dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.codespar/mcp-bigdatacorp is an MCP server published by codespar. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.byteplant-dev/byteplant-mcp |  io.github.codespar/mcp-bigdatacorp |
|---|---|---|
| Official MCP Registry | Listed, marked deprecated Version: 1.0.0 Downloads/month (PyPI): 256 Downloads/week (PyPI): 43 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.1.2 Downloads/month (npm): 145 Downloads/week (npm): 47 Forks (GitHub): 52 Stars (GitHub): 277 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | io.github.byteplant-dev/byteplant-mcp | io.github.codespar/mcp-bigdatacorp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (worse) | 277 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 52 (better) |
| Last release (differs) | 2026-10-18 | Not published |
| Where it runs (differs) | On your machine (byteplant-mcp) | On your machine (@codespar/mcp-bigdatacorp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 3 | 3, secrets among them: 2 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/byteplant-dev/byteplant-mcp | github.com/codespar/mcp-dev-latam |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
io.github.byteplant-dev/byteplant-mcp
An MCP server that provides Email, Phone and Address Validation Services from Byteplant
io.github.codespar/mcp-bigdatacorp
MCP server for BigDataCorp — Brazilian data enrichment + KYC (CPF/CNPJ/vehicle/property/antifraud)
How to run each
io.github.byteplant-dev/byteplant-mcp As a local MCP server: PyPI package
claude mcp add --env "AV_TOKEN=<YOUR_AV_TOKEN>" --env "EV_TOKEN=<YOUR_EV_TOKEN>" --env "PV_TOKEN=<YOUR_PV_TOKEN>" --transport stdio byteplant-mcp -- uvx byteplant-mcpRequires: AV_TOKEN (secret), EV_TOKEN (secret), PV_TOKEN (secret)
io.github.codespar/mcp-bigdatacorp As a local MCP server: npm package
claude mcp add --env "BIGDATACORP_ACCESS_TOKEN=<YOUR_BIGDATACORP_ACCESS_TOKEN>" --env "BIGDATACORP_TOKEN_ID=<YOUR_BIGDATACORP_TOKEN_ID>" --transport stdio mcp-bigdatacorp -- npx -y @codespar/mcp-bigdatacorpRequires: BIGDATACORP_ACCESS_TOKEN (secret), BIGDATACORP_TOKEN_ID (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only io.github.byteplant-dev/byteplant-mcp asks for
AV_TOKEN (secret)EV_TOKEN (secret)PV_TOKEN (secret)
Only io.github.codespar/mcp-bigdatacorp asks for
BIGDATACORP_ACCESS_TOKEN (secret)BIGDATACORP_API_BASEBIGDATACORP_TOKEN_ID (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.byteplant-dev/byteplant-mcp · What it can do: io.github.codespar/mcp-bigdatacorp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.