Statiko — Telegram trends & channel analytics is an MCP server with 10 tools an agent can call, among them fetch, get_channel_posts, get_channel_timeline. It answers at https://mcp.statiko.io/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 5 of 5 times since 13 September 2026; the last check, on 22 October 2026, succeeded.
Live Telegram data: trending topics, channel profiles & metrics, post history incl. edits/deletions.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
fetch | Fetch the full document behind a search result id: a channel profile with metrics, or a trending story with context and sample posts. Inputs: id |
get_channel_posts | 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 tex Inputs: channel, query, since, until, message_type, limit |
get_channel_timeline | 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. Inputs: channel, event_types, order, page, limit |
get_channels | 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 r Inputs: channels, start_date, end_date |
get_post_stats | 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_ Inputs: channel, message_id, since, until, bucket |
get_similar_channels | Channels that resemble the given one by category and audience — the peer cohort to compare a channel's metrics against. Inputs: channel, limit |
get_trend_samples | Sample Telegram posts that mention a trending topic, for reading what a story on the trending board is actually about. Inputs: norm, window, lang, limit |
get_trending_topics | 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. Inputs: window, lang, limit |
search | Search Statiko for tracked Telegram channels and currently trending stories. Returns document ids for the fetch tool; results cite statiko.io pages. Inputs: query |
search_channels | 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. Inputs: query, verified, categories, languages, activity, sort |
Every block below points at https://mcp.statiko.io/mcp. Pick your client and copy.
claude mcp add --transport http statiko-telegram-trends-channel https://mcp.statiko.io/mcp
{
"mcpServers": {
"statiko-telegram-trends-channel": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.statiko.io/mcp"]
}
}
}{
"mcpServers": {
"statiko-telegram-trends-channel": {
"url": "https://mcp.statiko.io/mcp"
}
}
}{
"servers": {
"statiko-telegram-trends-channel": {
"type": "http",
"url": "https://mcp.statiko.io/mcp"
}
}
}{
"context_servers": {
"statiko-telegram-trends-channel": {
"url": "https://mcp.statiko.io/mcp"
}
}
}{
"mcpServers": {
"statiko-telegram-trends-channel": {
"serverUrl": "https://mcp.statiko.io/mcp"
}
}
}{
"mcpServers": {
"statiko-telegram-trends-channel": {
"url": "https://mcp.statiko.io/mcp"
}
}
}name: Statiko — Telegram trends & channel analytics
version: 0.0.1
schema: v1
mcpServers:
- name: Statiko — Telegram trends & channel analytics
type: streamable-http
url: https://mcp.statiko.io/mcp{
"mcpServers": {
"statiko-telegram-trends-channel": {
"httpUrl": "https://mcp.statiko.io/mcp"
}
}
}{
"mcpServers": {
"statiko-telegram-trends-channel": {
"type": "http",
"url": "https://mcp.statiko.io/mcp"
}
}
}{
"mcpServers": {
"statiko-telegram-trends-channel": {
"url": "https://mcp.statiko.io/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.statiko.io%2Fmcp&type=streamable_http&id=statiko-telegram-trends-channel&name=Statiko%20%E2%80%94%20Telegram%20trends%20%26%20channel%20analytics
It answered our last check on 22 October 2026 in 371 ms. Over 5 checks since 13 September 2026 it answered 5. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by statiko.io and served from mcp.statiko.io, the vendor's own domain: https://mcp.statiko.io/mcp.
10, as returned by the server's own tools/list on 24 September 2026: fetch, get_channel_posts, get_channel_timeline, get_channels, get_post_stats, get_similar_channels, get_trend_samples, get_trending_topics, and 2 more.
It answered our last check on 22 October 2026 in 371 ms. Over 5 checks since 13 September 2026 it answered 5.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.statiko.io/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.statiko. Endpoint host: mcp.statiko.io. ARD identifier: urn:air:io.statiko:mcp:telegram.
First indexed 13 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.