Ext Ops Panel
Open dashboard
Comparison

imessage vs Bulk Phone Number Validator & Cleaner: Carrier, CSV or Sheet

imessage is a plugin bundle for AI coding tools published by anthropics. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-official). Bulk Phone Number Validator & Cleaner: Carrier, CSV or Sheet is an MCP server published by Nero-Engine. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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

Where each is published
MarketplaceimessageBulk Phone Number Validator & Cleaner: Carrier, CSV or Sheet
Claude Code: claude-plugins-official Listed
Version: 0.2.0
Forks (GitHub): 4 580
Stars (GitHub): 43 312
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
No figure published
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

imessage vs Bulk Phone Number Validator & Cleaner: Carrier, CSV or Sheet
FactimessageBulk Phone Number Validator & Cleaner: Carrier, CSV or Sheet
Marketplaces that list it11
Stars (GitHub) (differs)43 312No figure on GitHub
Forks (GitHub) (differs)4 580No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.apify.com)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)3Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/anthropics/claude-plugins-officialNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days ago, requires a key

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

imessage

In its own words, on Claude Code: claude-plugins-official:

iMessage messaging bridge with built-in access control. Reads chat.db directly, sends via AppleScript. Manage pairing, allowlists, and policy via /imessage:access.

Bulk Phone Number Validator & Cleaner: Carrier, CSV or Sheet

In its own words, on Official MCP Registry:

Bulk phone validation for an Apify dataset, CSV/Excel/JSON file or Google Sheet

How to run each

imessage As a Claude Code plugin

Claude Code
/plugin install imessage@claude-plugins-official

Bulk Phone Number Validator & Cleaner: Carrier, CSV or Sheet

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Bulk Phone Number Validator & Cleaner: Carrier, CSV or Sheet 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: imessage · What it can do: Bulk Phone Number Validator & Cleaner: Carrier, CSV or Sheet · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built