Ext Ops Panel
Open dashboard
Comparison

Telnyx vs io.github.tusk80/fastx402

Telnyx is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.tusk80/fastx402 is an MCP server published by tusk80. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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

Where each is published
MarketplaceTelnyxio.github.tusk80/fastx402
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.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

Telnyx vs io.github.tusk80/fastx402
FactTelnyxio.github.tusk80/fastx402
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)Not published2026-10-17
Where it runs (differs)Remote server (api.telnyx.com/v2/mcp)On your machine (fastx402-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 14, secrets among them: 2
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/tusk80/fastx402-mcp
Changes in the last 7 days (differs)03
First seen (differs)2026-10-112026-10-17
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

In its own words, on Docker MCP Catalog:

Enables interaction with powerful telephony, messaging, and AI assistant APIs.

io.github.tusk80/fastx402

In its own words, on Official MCP Registry:

60+ pay-per-call tools for agents (data, dates, QR, crypto, web), paid in USDC via x402.

How to run each

Telnyx As a remote MCP server

Claude Code
claude mcp add --transport http telnyx https://api.telnyx.com/v2/mcp

Requires: TELNYX_API_KEY (secret)

io.github.tusk80/fastx402 As a local MCP server: npm package

Claude Code
claude mcp add --env "FASTX402_EVM_PRIVATE_KEY=<YOUR_FASTX402_EVM_PRIVATE_KEY>" --env "FASTX402_SOLANA_PRIVATE_KEY=<YOUR_FASTX402_SOLANA_PRIVATE_KEY>" --transport stdio fastx402 -- npx -y fastx402-mcp

Requires: FASTX402_EVM_PRIVATE_KEY (secret), FASTX402_SOLANA_PRIVATE_KEY (secret)

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 io.github.tusk80/fastx402 asks for

  • FASTX402_EVM_PRIVATE_KEY (secret)
  • FASTX402_MAX_USD_PER_CALL
  • FASTX402_MAX_USD_PER_DAY
  • FASTX402_SOLANA_PRIVATE_KEY (secret)

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.tusk80/fastx402 · 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.

Where the data comes from: how the catalog is built