Statiko — Telegram trends & channel analytics

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Live Telegram data: trending topics, channel profiles & metrics, post history incl. edits/deletions.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Statiko — Telegram trends & channel analytics": {
      "url": "https://mcp.statiko.io/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (10)

• get_trending_topics read-only

  Ranked board of trending topics (stories) across tracked Telegram channels for a rolling 24h window. Each story carries a headline, context paragraph, member keywords, mention/channel counts, momentum and an hourly sparkline.

  Parameters:

  • lang — string — ISO-639-1 language code of the board, defaulting to 'ru'. Boards are per-language; pick the language the audience posts in.
  • limit — integer — Number of stories to return
  • window — string — Rolling 24h window to rank: 'now' (live) or 'yesterday'

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• get_trend_samples read-only

  Sample Telegram posts that mention a trending topic, for reading what a story on the trending board is actually about.

  Parameters:

  • norm (required) — string — Normalized topic key of the story ('norm' field from get_trending_topics)
  • lang — string — ISO-639-1 language code of the board, defaulting to 'ru'. Boards are per-language; pick the language the audience posts in.
  • limit — integer
  • window — string

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• search_channels read-only

  Search Statiko's catalog of tracked Telegram channels by name and filter by verification, category, language and activity. Returns channel slugs to use with get_channels and get_channel_posts.

  Parameters:

  • sort — string — Sort order: 'subs' (largest first, default) or 'name'
  • limit — integer
  • query — string — Channel name or username to match; omit to browse by filters
  • activity — array — Last-post activity buckets to filter by (any match)
  • verified — boolean — true = verified channels only, false = unverified only
  • languages — array — ISO-639-1 language codes to filter by (any match)
  • categories — array — Category slugs to filter by; a channel matching any one passes

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• get_channels read-only

  One channel: full profile of a tracked Telegram channel — description, subscriber and post counts, categories, AI insights, and metrics (subscriber growth, post frequency, view rate, engagement) with dated sparklines over an optional date range. Several channels (up to 10, ids and slugs mixed): compact comparison rows with headline metric values and changes over the last 30 days, from one lookup; unknown entries are listed as unresolved instead of failing the call.

  Parameters:

  • channels (required) — array — Channel slug (Telegram username, without the @) or numeric channel ids, mixed freely. One channel answers its full profile; several answer compact comparison rows.
  • end_date — string — Metrics window end (YYYY-MM-DD, inclusive); default today. Single channel only
  • start_date — string — Metrics window start (YYYY-MM-DD, inclusive); default -30d. Single channel only

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• get_channel_timeline read-only

  Structural events in a channel's history: renames, description and photo changes, verification flips, subscriber/view milestones, and post edits or deletions — for telling what happened on a given date.

  Parameters:

  • channel (required) — string — Channel slug (Telegram username, without the @) or numeric channel id
  • page — integer
  • limit — integer
  • order — string — Sort by event time: desc (newest first) or asc
  • event_types — array — Event types to keep; omit for all of them

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• get_similar_channels read-only

  Channels that resemble the given one by category and audience — the peer cohort to compare a channel's metrics against.

  Parameters:

  • channel (required) — string — Channel slug (Telegram username, without the @) or numeric channel id
  • limit — integer

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• get_channel_posts read-only

  Recent posts from a tracked Telegram channel, newest first, with text, view/forward/reply/reaction counts and `reactions_map`, the five most used reaction emoji with their counts. Accepts a channel slug or a numeric chat id, an optional text `query` to search the channel's posts, and an optional time range. Album posts are collapsed to one row, so a page may hold fewer than `limit` posts.

  Parameters:

  • channel (required) — string — Channel slug (Telegram username, without the @) or numeric channel id
  • limit — integer
  • query — string — Only posts whose text contains this term (case-insensitive substring)
  • since — string — Only posts at or after this ISO 8601 timestamp
  • until — string — Only posts before this ISO 8601 timestamp
  • message_type — string — Filter by message type: TEXT, PHOTO, VIDEO, AUDIO, DOCUMENT, UNSUPPORTED (case-insensitive)

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• get_post_stats read-only

  How a post's views, forwards, replies and reactions (total and per-emoji) evolved over its life, as a sparse series of snapshots bucketed per hour or per day, oldest first — for view velocity and reaction drift. `message_id` comes from get_channel_posts. A post with no recorded snapshots answers an empty series.

  Parameters:

  • channel (required) — string — Channel slug (Telegram username, without the @) or numeric channel id
  • message_id (required) — integer — Post id within the channel
  • since — string — Only snapshots taken at or after this ISO 8601 timestamp
  • until — string — Only snapshots taken before this ISO 8601 timestamp
  • bucket — string — Series resolution: one snapshot per hour (1h) or day (1d)

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• search read-only

  Search Statiko for tracked Telegram channels and currently trending stories. Returns document ids for the fetch tool; results cite statiko.io pages.

  Parameters:

  • query (required) — string — Free-text search query

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• fetch read-only

  Fetch the full document behind a search result id: a channel profile with metrics, or a trending story with context and sample posts.

  Parameters:

  • id (required) — string — Document id from a previous search: 'channel:<slug>' or 'trend:<window>:<lang>:<norm>'

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.