phone-validator vs io.github.cameron-creations/numberbroom-mcp
phone-validator is no longer listed on any marketplace we read: these are its last known data, as of 2026‑11‑03.
phone-validator is a plugin bundle for AI coding tools published by DataSift. No marketplace we read lists it any more. io.github.cameron-creations/numberbroom-mcp is an MCP server published by cameron-creations. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.cameron-creations/numberbroom-mcp | |
|---|---|---|
| Community marketplace datasift-ty-personal/siftstack | Removed on 2026-11-03 Version: not stated Forks (GitHub): 23 Stars (GitHub): 23 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 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 | phone-validatorno longer listed · | io.github.cameron-creations/numberbroom-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 23 | 0 |
| Forks (GitHub) (differs) | 23 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (numberbroom.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/datasift-ty-personal/siftstack | github.com/cameron-creations/numberbroom-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 24 h ago, requires authentication |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of phone-validator
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Bulk Phone Number Validator & Cleaner: Carrier, CSV or Sheet
Bulk phone validation for an Apify dataset, CSV/Excel/JSON file or Google Sheet
-
Validate emails (MX, disposable, role, typo) and phone numbers, singly or in batches, for AI agents.
-
Veriphone MCP — wraps the Veriphone phone-validation API (veriphone.io)
-
data247 io.github.LogicTreeInc/data247
Phone carrier lookup, append, verification, DNC, and fraud data services.
-
data-cleanup: fix a messy CSV before you load it
Fix messy CSVs in one call: trim, ISO dates, normalize emails/phones, flag dupes. x402 $0.005, Base
-
Local stdio phone metadata and email syntax/DNS checks. Not live carrier or mailbox verification.
What each says it does
phone-validator
Score and validate phone numbers via Trestle's phone_intel API, then generate DataSift/REISift-ready CSVs with phone tags for upload.
io.github.cameron-creations/numberbroom-mcp
Verify US phone numbers: line type, carrier, and TCPA litigator status via the NumberBroom API.
How to run each
phone-validator
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.cameron-creations/numberbroom-mcp As a remote MCP server
claude mcp add --transport http numberbroom-mcp https://numberbroom.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.cameron-creations/numberbroom-mcp 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
Neither one's marketplaces publish the settings it asks for.
What it can do: phone-validator · What it can do: io.github.cameron-creations/numberbroom-mcp · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.