io.github.apitier/mcp-server vs io.github.mrfentmen/phone-validator-mcp
io.github.apitier/mcp-server is an MCP server published by apitier. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.mrfentmen/phone-validator-mcp is an MCP server published by mrfentmen. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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 | ||
|---|---|---|
| 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: 1.0.0 Downloads/month (npm): 701 Downloads/week (npm): 143 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 | io.github.mrfentmen/phone-validator-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@apitier/mcp-server) | On your machine (phone-validator-mcp) |
| Transport | stdio | stdio |
| 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/mrfentmen/phone-validator-mcp |
| 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.apitier/mcp-server
APITier utility APIs as MCP tools: validation, UK/India address lookup, barcode/QR, data conversion.
io.github.mrfentmen/phone-validator-mcp
Validate and format international phone numbers locally. No network and no key.
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-server
Requires: 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)
io.github.mrfentmen/phone-validator-mcp As a local MCP server: npm package
claude mcp add --transport stdio phone-validator-mcp -- npx -y phone-validator-mcp
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
The marketplaces of io.github.mrfentmen/phone-validator-mcp 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: io.github.mrfentmen/phone-validator-mcp · 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.