Telnyx vs io.github.vaemail/vaemail
Telnyx is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.vaemail/vaemail is an MCP server published by vaemail. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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 |  io.github.vaemail/vaemail | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.0 Downloads/month (npm): 230 Downloads/week (npm): 32 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 | io.github.vaemail/vaemail |
|---|---|---|
| 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 (vaemail) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 2, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/vaemail/vaemail-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | 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.
io.github.vaemail/vaemail
Email infrastructure for AI agents: send, authenticate domains, track delivery, diagnose issues.
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)
io.github.vaemail/vaemail As a local MCP server: npm package
claude mcp add --env "VAEMAIL_API_KEY=<YOUR_VAEMAIL_API_KEY>" --transport stdio vaemail -- npx -y vaemail mcpRequires: VAEMAIL_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
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 io.github.vaemail/vaemail asks for
VAEMAIL_API_KEY (secret)VAEMAIL_BASE_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Telnyx · What it can do: io.github.vaemail/vaemail · 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.