Telegram Context MCP vs Telegram Channel Scraper
Telegram Context MCP is an MCP server published by egor-fedorov. Marketplaces we read that list it: 1 (Official MCP Registry). Telegram Channel Scraper is an MCP server published by sumitrmardy. 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 |  Telegram Context MCP |  Telegram Channel Scraper |
|---|---|---|
| Official MCP Registry | Listed Version: 0.6.0 Forks (GitHub): 1 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 1.0.0 No figure published 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 | Telegram Context MCP | Telegram Channel Scraper |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 | No figure on GitHub |
| Forks (GitHub) (differs) | 1 | No figure on GitHub |
| Last release (differs) | 2026-10-29 | Not published |
| Where it runs (differs) | On your machine (telegram-context-mcp) | Remote server (mcp.apify.com) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/egor-fedorov/telegram-mcp | Not stated |
| Changes in the last 7 days (differs) | 4 | 2 |
| First seen (differs) | 2026-10-27 | 2026-10-28 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-24 |
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
Telegram Context MCP
Read permitted Telegram chats, retrieve original posts and files, and track changes locally.
Telegram Channel Scraper
Public Telegram channel messages, views and reactions without login. Flat rows, never null.
How to run each
Telegram Context MCP As a local MCP server: PyPI package
claude mcp add --transport stdio telegram-mcp -- uvx --python 3.12 telegram-context-mcp serveTelegram Channel Scraper
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Telegram Channel Scraper 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
Neither one's marketplaces publish the settings it asks for.
What it can do: Telegram Context MCP · What it can do: Telegram Channel Scraper · 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.