Hackle vs io.github.mrfentmen/telegram-mcp
Hackle is an MCP server published by hackle-io. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). io.github.mrfentmen/telegram-mcp is an MCP server published by mrfentmen. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. 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 |  Hackle | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 3 Stars (GitHub): 3 Not marked · First seen |
Listed Version: 1.1.0 Downloads/month (npm): 749 Downloads/week (npm): 69 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:b45e8e1c6390 Forks (GitHub): 3 Pulls (Docker Hub): 16 450 Stars (Docker Hub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
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 | Hackle | io.github.mrfentmen/telegram-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 3 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 16 450 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 3 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server or your machine | On your machine (@mrfentmen/telegram-mcp) |
| Transport (differs) | Streamable HTTP, stdio | stdio |
| Tools it declares (differs) | 19 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/hackle-io/hackle-mcp | github.com/mrfentmen/premium-mcps |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-17 |
| Endpoint at the last check (differs) | Responded 21 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
Hackle
Remote MCP server for the Hackle Admin API: experiments, feature flags, remote config, messaging.
io.github.mrfentmen/telegram-mcp
Use the Telegram Bot API (free bot; set TELEGRAM_BOT_TOKEN): bot info, send messages, read updates.
How to run each
Hackle As a remote MCP server
claude mcp add --transport http hackle-mcp https://mcp.hackle.io/mcpio.github.mrfentmen/telegram-mcp As a local MCP server: npm package
claude mcp add --transport stdio telegram-mcp -- npx -y @mrfentmen/telegram-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Hackle has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of io.github.mrfentmen/telegram-mcp publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of io.github.mrfentmen/telegram-mcp publish no settings it asks for, so we do not compare settings.
What it can do: Hackle · What it can do: io.github.mrfentmen/telegram-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.