dev.kanta/cli vs Sendy SMS
dev.kanta/cli is an MCP server published by kanta.dev. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Sendy SMS is an MCP server published by sendy.co.il. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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 |  dev.kanta/cli |  Sendy SMS |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.8 Downloads/month (npm): 880 Downloads/week (npm): 785 Not marked · First seen |
Listed Version: 1.1.0 No figure published Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 0.1.8 Downloads/month (npm): 880 Downloads/week (npm): 785 Not marked · First seen |
Not listed |
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 | dev.kanta/cli | Sendy SMS |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Last release (differs) | 2026-10-15 (worse) | 2026-10-28 (better) |
| Where it runs (differs) | On your machine (@kantadev/cli) | Remote server (sendy.co.il/api/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/griffinkanta/kanta-dev | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-25 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 44 h ago returned HTTP 401 |
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
dev.kanta/cli
Kanta Verify, Find, and Database: email verification, email finding, and B2B contact search.
Sendy SMS
Send SMS, verify phone numbers with one-time codes (OTP) and manage contacts in Israel.
How to run each
dev.kanta/cli As a local MCP server: npm package
claude mcp add --env "KANTA_API_KEY=<YOUR_KANTA_API_KEY>" --transport stdio cli -- npx -y @kantadev/cli mcpRequires: KANTA_API_KEY (secret)
Sendy SMS As a remote MCP server
claude mcp add --transport http sms https://sendy.co.il/api/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 Sendy SMS 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 Sendy SMS publish no settings it asks for, so we do not compare settings.
What it can do: dev.kanta/cli · What it can do: Sendy SMS · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.