Telnyx vs eSIM.dog MCP Server
Telnyx is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). eSIM.dog MCP Server is an MCP server published by elliot-esimdog. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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 |  Telnyx |  eSIM.dog MCP Server |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.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
| Fact | Telnyx | eSIM.dog MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.telnyx.com/v2/mcp) | Not stated |
| Transport (differs) | Streamable HTTP | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/elliot-esimdog/mcp-esim |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 404 (5 days ago) | no remote endpoint we check |
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
Telnyx
Enables interaction with powerful telephony, messaging, and AI assistant APIs.
eSIM.dog MCP Server
Provision global eSIM data plans and real mobile phone numbers for AI agents. 200+ countries.
How to run each
Telnyx As a remote MCP server
claude mcp add --transport http telnyx https://api.telnyx.com/v2/mcpRequires: TELNYX_API_KEY (secret)
eSIM.dog MCP Server
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Telnyx 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 eSIM.dog MCP Server publish no settings it asks for, so we do not compare settings.
What it can do: Telnyx · What it can do: eSIM.dog MCP Server · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.