imessage vs SMS Validator API
imessage is a plugin bundle for AI coding tools published by linq-team. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). SMS Validator API is an MCP server published by Br0ski777. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 |  imessage |  SMS Validator API |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.2.0 Forks (GitHub): 3 Stars (GitHub): 25 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.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 | imessage | SMS Validator API |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 25 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 3 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (sms-validator.api.klymax402.com/mcp) |
| Transport (differs) | Not stated | SSE |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 5 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/linq-team/claude-code-imessage-channel | github.com/br0ski777/sms-validator-x402 |
| 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 | Not responding since 2026-10-15 |
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
Two-way iMessage bridge for Claude Code. Send and receive iMessages, photos, reactions, threaded replies, and file attachments directly from your Claude Code session. Powered by Linq's iMessage API with built-in access control (pairing codes, allowlists, open/disabled policies). Supports 15 iMessage effects (confetti, fireworks, etc.), text decorations (bold, italic, animations), rich link previews, SMS/RCS fallback, and capability checks. Auto-sets contact card, sends read receipts and typing indicators.
SMS Validator API
Validate SMS-capable phone numbers — mobile vs landline, E.164 format. x402 micropayment.
How to run each
imessage As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install imessage@claude-communitySMS Validator API As a remote MCP server
claude mcp add --transport sse sms-validator https://sms-validator.api.klymax402.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only SMS Validator API 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: SMS Validator API · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/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.