Ext Ops Panel
Open dashboard
Comparison

LINE vs Telegram Channel Scraper - Posts, Media & Buttons | No Login

LINE is an MCP server published by line. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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). As of our marketplace pass on 2026-10-18. 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
MarketplaceLINETelegram Channel Scraper - Posts, Media & Buttons | No Login
Docker MCP Catalog Listed
Version: sha256:2fe78452545d
Forks (GitHub): 160
Pulls (Docker Hub): 24 938
Stars (Docker Hub): 0
Stars (GitHub): 789
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.3
Forks (GitHub): 0
Stars (GitHub): 1
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

LINE vs Telegram Channel Scraper - Posts, Media & Buttons | No Login
FactLINETelegram Channel Scraper - Posts, Media & Buttons | No Login
Marketplaces that list it11
Stars (GitHub) (differs)789 (better)1 (worse)
Pulls (Docker Hub) (differs)24 938No figure on Docker Hub
Forks (GitHub) (differs)160 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/line)Remote server (mcp.apify.com)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)12Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/line/line-bot-mcp-servergithub.com/anshumanatrey/telegram-channel-scraper
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 17 h ago, requires a key

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

LINE

In its own words, on Docker MCP Catalog:

MCP server that integrates the LINE Messaging API to connect an AI Agent to the LINE Official Account.

Telegram Channel Scraper - Posts, Media & Buttons | No Login

In its own words, on Official MCP Registry:

Telegram Channel Scraper - No Login, $0.30 per 1K Posts

How to run each

LINE As a local MCP server: Docker image

Claude Code
claude mcp add --env "CHANNEL_ACCESS_TOKEN=<YOUR_CHANNEL_ACCESS_TOKEN>" --transport stdio line -- docker run -i --rm -e CHANNEL_ACCESS_TOKEN mcp/line

Requires: CHANNEL_ACCESS_TOKEN (secret)

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

Commands 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

The marketplaces of Telegram Channel Scraper - Posts, Media & Buttons | No Login publish no list of tools, so we do not compare tools.

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: LINE · What it can do: Telegram Channel Scraper - Posts, Media & Buttons | No Login · 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