io.github.apitier/mcp-server vs Busca de CEP
io.github.apitier/mcp-server is an MCP server published by apitier. Marketplaces we read that list it: 1 (Official MCP Registry). Busca de CEP is an MCP server published by mcp-dir. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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.apitier/mcp-server |  Busca de CEP |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.2 Downloads/month (npm): 149 Downloads/week (npm): 19 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 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.apitier/mcp-server | Busca de CEP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@apitier/mcp-server) | Remote server (api.mcp.ai/p_busca_cep) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 7, secrets among them: 7 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/apitier/apitier-mcp-server | github.com/mcp-dir/busca_cep-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 10 h ago |
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.apitier/mcp-server
APITier utility APIs as MCP tools: validation, UK/India address lookup, barcode/QR, data conversion.
Busca de CEP
Returns the postal code (CEP) and standardized address from the Brazilian Post from a given address.
How to run each
io.github.apitier/mcp-server As a local MCP server: npm package
claude mcp add --env "APITIER_BARCODE_KEY=<YOUR_APITIER_BARCODE_KEY>" --env "APITIER_CONVERT_DATA_KEY=<YOUR_APITIER_CONVERT_DATA_KEY>" --env "APITIER_EMAIL_KEY=<YOUR_APITIER_EMAIL_KEY>" --env "APITIER_PHONE_KEY=<YOUR_APITIER_PHONE_KEY>" --env "APITIER_PINCODE_KEY=<YOUR_APITIER_PINCODE_KEY>" --env "APITIER_POSTCODE_KEY=<YOUR_APITIER_POSTCODE_KEY>" --env "APITIER_VAT_KEY=<YOUR_APITIER_VAT_KEY>" --transport stdio io-github-apitier-mcp-server -- npx -y @apitier/mcp-serverRequires: APITIER_BARCODE_KEY (secret), APITIER_CONVERT_DATA_KEY (secret), APITIER_EMAIL_KEY (secret), APITIER_PHONE_KEY (secret), APITIER_PINCODE_KEY (secret), APITIER_POSTCODE_KEY (secret), APITIER_VAT_KEY (secret)
Busca de CEP As a remote MCP server
claude mcp add --transport http busca-cep-mcp https://api.mcp.ai/p_busca_cepCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Busca de CEP has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Busca de CEP publish no settings it asks for, so we do not compare settings.
What it can do: io.github.apitier/mcp-server · What it can do: Busca de CEP · 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.