Data · Remote MCP server
Telegram Channel Scraper
Public Telegram channel posts, views, reactions, media and subscriber counts. No login needed.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.brenton-keller/telegram-channel-scraper- Version
- 0.1.0
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP
- Published
- 2026-09-08
- Updated
- 2026-09-08
- Publisher
- brenton-keller (GitHub) · 5 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/brenton-keller) · how
- Listed under
- Telegram MCP servers
- Website
- apify.com/brenton8907/telegram-channel-scraper
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.apify.com/?tools=brenton8907/telegram-channel-scraper | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; a Bearer token is asked for
- Checked on
- 2026-10-05
How to connect Telegram Channel Scraper
Telegram Channel Scraper is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.apify.com/?tools=brenton8907/telegram-channel-scraper, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from brenton-keller (GitHub)
| Server | Runs |
|---|---|
| Google Ads Transparency Center ScraperGoogle Ads by domain or brand: creatives, formats, dates; or bulk-check which domains advertise. | Remote · HTTPLive check: sign-in required |
| PDF Text, Table and OCR ExtractorPDF URLs to per-page text, tables as rows, Markdown, metadata and OCR for scanned pages. | Remote · HTTPLive check: sign-in required |
| Prediction Markets Data: Kalshi + PolymarketLive Kalshi + Polymarket prices, orderbooks, trades, results. Pay per result via Apify. | Remote · HTTPLive check: sign-in required |
| Product Hunt Data (Official API)Product Hunt launches, votes, makers, comments via the official API. Pay per result. | Remote · HTTPLive check: sign-in required |
More data servers
| Server | Runs |
|---|---|
| Tee TimesLive golf tee time availability across US courses. Search by location, date, players, and price. | Remote · HTTPLive check: ✗ no handshake |
| TelaSelf-hostable team wiki; agents read & write it via MCP; Atlas turns your repo into a cited wiki. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Telegram Archive MCPMCP server for Telegram Archive - search messages, browse chats, and access history. | Local · stdio |
| Telegram Business MCPSelf-hosted Telegram Business MCP: search chats, read files and transcripts, optionally reply. | Remote · HTTP |
| Telegram Channel ScraperPublic Telegram channel posts without login: text, views, reactions, media, exact subscribers. | Remote · HTTPLive check: sign-in required |
| Telegram Channel Scraper MCPScrape messages, extract leads from public Telegram channels. No login required. | Local · stdio |
| Telegram MCPTelegram MCP server: read, send, and search messages and manage chats via your account. | Local · stdio |
| Telemost MCP ServerTelegram channel analytics and statistics for AI agents, pay-per-call in USDC via x402. | Remote & Local · HTTP, stdioLive check: ✓ handshake |