Tgatlas

io.github.starnikovolegPublished by GitHub account starnikovolegv0.1.2Updated Oct 24, 2026

Public Telegram channels for agents: profiles, posting cadence, and similar-channel discovery.

VerifiedSTDIODesktop onlyWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Local MCP server that lets an assistant look up public Telegram channel profiles, posting cadence, and Telegram-recommended similar channels.

What you can do
Look up a public channel's profile: title, description, subscriber count, creation date, verification and scam flags, and posting cadence, with cadence optionally skipped to save calls. Find channels Telegram recommends alongside a given one, optionally enriching results with exact subscriber counts. Search Telegram's global index of public channels and groups to find a starting point. Return results as Markdown by default or raw JSON for code pipelines.
When to use it
Useful when you need to assess public Telegram channels by activity rather than follower count alone, or to discover related channels by walking outward from known seeds. It only covers public channel metadata, not message contents, member lists, or private groups.
Requirements
Runs locally via npx, so Node.js is needed. Requires a RapidAPI key supplied as TELEGRAM_API_KEY (RAPIDAPI_KEY also works); a free tier exists. Optional TELEGRAM_API_HOST and TELEGRAM_TIMEOUT_MS variables. Network access to the upstream RapidAPI host.
Before you install
The RapidAPI key is a secret passed by environment variable. RapidAPI bills per request: a channel lookup costs two or three calls, similar-channel lookups cost two plus one per enriched result, so usage can incur charges beyond the free tier. Lookups are read-only and limited to public channel metadata.

Installation

In SourceWeft

  1. Open Tgatlas in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Image]

tgatlas-mcp

MCP server for public Telegram channels. Gives an agent a channel's real profile — subscribers, description, creation date, verification and scam flags, how often it posts — and the channels Telegram itself considers similar to it.

No phone number, no session file, no MTProto client to keep alive. An API key and a Node runtime.

Install

bash
npx tgatlas-mcp

Claude Desktop / Claude Code / any MCP client:

json
{  "mcpServers": {    "tgatlas": {      "command": "npx",      "args": ["-y", "tgatlas-mcp"],      "env": { "TELEGRAM_API_KEY": "your-rapidapi-key" }    }  }}

Get a key at rapidapi.com/starnikovoleg/api/telegram155. There is a free tier and no card.

Tools

telegram_channel

A channel's profile: title, description, exact subscriber count, creation date, Telegram's own verification and scam flags, and posting cadence.

The cadence is the part most directories leave out, and it is usually the answer to the question being asked. A channel with 200,000 subscribers and nothing published in fourteen months looks identical to a live one in every listing that reports only follower counts.

@durov — Du rov's ChannelSubscribers   1,400,000Created       2017-02-15Last post     2026-08-29Posting rate  0.4 posts/day over the last 30

telegram_similar_channels

The channels Telegram recommends alongside a given one — its own topical judgement rather than a keyword match, so it returns channels that share an audience without sharing vocabulary.

This is how you find channels whose names you do not already know: start from one you do and walk outward. Two rounds of expansion from a few dozen seeds reaches several thousand channels.

Set enrich: true to fetch exact subscriber counts for each result.

telegram_search_channels

Telegram's global search over public channels and groups. Use it to find a starting point; use telegram_similar_channels to expand it.

Output

Markdown by default — what a model reads without a parsing step. Pass format: "json" for the raw API response when you are piping into code.

Scope

Public channel metadata only. Message contents, member lists, and private groups are outside what this reads and outside what it will return.

Cost

Tools call the REST endpoints directly rather than proxying a remote MCP endpoint. RapidAPI bills per request, so this arrangement means initialize and tools/list are free: you pay for lookups, not handshakes.

telegram_channel costs three calls with cadence on, two with cadence: false. telegram_similar_channels costs two, plus one per result when enrich: true (capped at 12).

Environment

VariableDefaultPurpose
TELEGRAM_API_KEY—RapidAPI key. RAPIDAPI_KEY also works.
TELEGRAM_API_HOSTtelegram155.p.rapidapi.comUpstream host.
TELEGRAM_TIMEOUT_MS30000Per-request timeout.

Related

TgAtlas publishes a weekly measured corpus built on the same API: channel directories by topic, the recommendation graph inverted into "who recommends this channel", and how those numbers move week to week.

MIT.

Source: README.md at commit 2d8d4e9

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 17, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts