Telegram Channel Scraper - Posts, Media & Buttons | No Login vs Better-TG-CLI (Telegram)
Telegram Channel Scraper - Posts, Media & Buttons | No Login is an MCP server published by AnshumanAtrey. Marketplaces we read that list it: 1 (Official MCP Registry). Better-TG-CLI (Telegram) is an MCP server published by TheVilfer. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). 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 Channel Scraper - Posts, Media & Buttons | No Login |  Better-TG-CLI (Telegram) |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.4 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.38.0 Downloads/month (npm): 3 900 Downloads/week (npm): 1 296 Forks (GitHub): 4 Stars (GitHub): 4 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.38.0 Downloads/month (npm): 3 900 Downloads/week (npm): 1 296 Forks (GitHub): 4 Stars (GitHub): 4 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 Channel Scraper - Posts, Media & Buttons | No Login | Better-TG-CLI (Telegram) |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 1 (worse) | 4 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 4 (better) |
| Last release (differs) | 2026-10-29 (better) | 2026-10-19 (worse) |
| Where it runs (differs) | Remote server (mcp.apify.com) | On your machine (better-tg-cli) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/anshumanatrey/telegram-channel-scraper | github.com/thevilfer/better-tg-cli |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-24 | 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
Telegram Channel Scraper - Posts, Media & Buttons | No Login
Telegram Channel Scraper - No Login, $0.30 per 1K Posts
Better-TG-CLI (Telegram)
Telegram on your own account: read, search, send and press bot buttons. Writes need your approval.
How to run each
Telegram Channel Scraper - Posts, Media & Buttons | No Login
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: Authorization header
Better-TG-CLI (Telegram) As a local MCP server: npm package
claude mcp add --transport stdio better-tg-cli -- npx -y better-tg-cli mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Telegram Channel Scraper - Posts, Media & Buttons | No Login 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
The marketplaces of Telegram Channel Scraper - Posts, Media & Buttons | No Login publish no settings it asks for, so we do not compare settings.
What it can do: Telegram Channel Scraper - Posts, Media & Buttons | No Login · What it can do: Better-TG-CLI (Telegram) · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.