mcp-computeflux vs io.github.telegraphprotocol/telegraph
mcp-computeflux is an MCP server published by computeflux2026isgod. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.telegraphprotocol/telegraph is an MCP server published by telegraphprotocol. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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 |  mcp-computeflux |  io.github.telegraphprotocol/telegraph |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.0 Downloads/month (npm): 124 Downloads/week (npm): 16 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 | mcp-computeflux | io.github.telegraphprotocol/telegraph |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (https://github.com/computeflux2026isgod/mcp-computeflux/releases/download/v1.0.0.0/send_mcp-computeflux.mcpb) | On your machine (telegraph-protocol-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 8, secrets among them: 2 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/computeflux2026isgod/mcp-computeflux | github.com/telegraphprotocol/telegraph-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
mcp-computeflux
OpenAI-compatible multi-model inference via ComputeFlux (Polkadot testnet, TEE-verifiable). stdio.
io.github.telegraphprotocol/telegraph
Decentralized AI inference (weather, deepfake detection, LLMs) with x402 USDC micropayments.
How to run each
mcp-computeflux
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.telegraphprotocol/telegraph As a local MCP server: npm package
claude mcp add --env "TELEGRAPH_DAEMON_URL=<YOUR_TELEGRAPH_DAEMON_URL>" --env "TELEGRAPH_ENGINE_URL=<YOUR_TELEGRAPH_ENGINE_URL>" --env "TELEGRAPH_EVM_PRIVATE_KEY=<YOUR_TELEGRAPH_EVM_PRIVATE_KEY>" --env "TELEGRAPH_NODE_URL=<YOUR_TELEGRAPH_NODE_URL>" --env "TELEGRAPH_SOLANA_PRIVATE_KEY=<YOUR_TELEGRAPH_SOLANA_PRIVATE_KEY>" --transport stdio telegraph -- npx -y telegraph-protocol-mcpRequires: TELEGRAPH_DAEMON_URL, TELEGRAPH_ENGINE_URL, TELEGRAPH_EVM_PRIVATE_KEY (secret), TELEGRAPH_NODE_URL, TELEGRAPH_SOLANA_PRIVATE_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
The marketplaces of mcp-computeflux publish no settings it asks for, so we do not compare settings.
What it can do: mcp-computeflux · What it can do: io.github.telegraphprotocol/telegraph · Compare two other plugins
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.