Telnyx vs Signal Messaging (via signal-cli)
Telnyx is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Signal Messaging (via signal-cli) is an MCP server published by joshuawowk. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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 | ||
|---|---|---|
| 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.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 | Telnyx | Signal Messaging (via signal-cli) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.telnyx.com/v2/mcp) | On your machine (ghcr.io/joshuawowk/signal-mcp:1.0.1) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 8, secrets among them: 0 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/joshuawowk/signal-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-20 |
| Endpoint at the last check (differs) | Answered with HTTP 404 (16 h 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.
Signal Messaging (via signal-cli)
Send Signal messages and read replies through your own signal-cli JSON-RPC daemon (unofficial).
How to run each
Telnyx As a remote MCP server
claude mcp add --transport http telnyx https://api.telnyx.com/v2/mcp
Requires: TELNYX_API_KEY (secret)
Signal Messaging (via signal-cli) As a local MCP server: Docker image
claude mcp add --env "SIGNAL_DEFAULT_RECIPIENT=<YOUR_SIGNAL_DEFAULT_RECIPIENT>" --env "SIGNAL_SENDER=<YOUR_SIGNAL_SENDER>" --transport stdio signal-mcp -- docker run -i --rm -e SIGNAL_DEFAULT_RECIPIENT -e SIGNAL_SENDER -i --add-host host.docker.internal:host-gateway ghcr.io/joshuawowk/signal-mcp:1.0.1 python3 /app/server.py
Requires: SIGNAL_DEFAULT_RECIPIENT, SIGNAL_SENDER
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
Only Telnyx asks for
TELNYX_API_KEY (secret)
Only Signal Messaging (via signal-cli) asks for
SIGNAL_DEFAULT_RECIPIENTSIGNAL_INBOX_PATHSIGNAL_INBOX_RETENTION_DAYSSIGNAL_POLL_INTERVALSIGNAL_RPC_URLSIGNAL_SENDERSIGNAL_TCP_HOSTSIGNAL_TCP_PORT
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Telnyx · What it can do: Signal Messaging (via signal-cli) · 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.