# Statiko — Telegram trends & channel analytics (remote · mcp.statiko.io)

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

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.statiko.io`: 80/100 (this document), [markdown](https://verifymcp.io/servers/io-statiko-telegram/mcp.md), [page](https://verifymcp.io/servers/io-statiko-telegram/mcp)

## Channel facts

- Endpoint: `https://mcp.statiko.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1255 tokens (~125/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 81% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Statiko — Telegram trends & channel analytics MCP server?

Statiko — Telegram trends & channel analytics is a hosted endpoint at https://mcp.statiko.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-statiko-telegram 'https://mcp.statiko.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-statiko-telegram": {
      "url": "https://mcp.statiko.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-statiko-telegram": {
      "type": "http",
      "url": "https://mcp.statiko.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-statiko-telegram]
url = "https://mcp.statiko.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-statiko-telegram": {
      "type": "remote",
      "url": "https://mcp.statiko.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-statiko-telegram --url 'https://mcp.statiko.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-statiko-telegram:
    url: "https://mcp.statiko.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-statiko-telegram": {
      "Transport": "http",
      "Url": "https://mcp.statiko.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-statiko-telegram -t streamable-http -u 'https://mcp.statiko.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-statiko-telegram": {
      "type": "http",
      "url": "https://mcp.statiko.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 77, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-13 (score 77)

First indexed and scored.

## MCP tools (10)

### `get_trending_topics` (~126 tokens)

Trending topics board

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.

Input 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'

Output parameters:

- `computed_at`
- `items` (array)
- `lang` (string)
- `languages`
- `url` (string)
- `window` (string)
- `window_end`
- `window_start`

### `get_trend_samples` (~105 tokens)

Posts behind a trend

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

Input 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)
- `norm` (string, required): Normalized topic key of the story ('norm' field from get_trending_topics)
- `window` (string)

Output parameters:

- `lang` (string)
- `norm` (string)
- `samples` (array)
- `window` (string)

### `search_channels` (~167 tokens)

Search Telegram 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.

Input parameters:

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

Output parameters:

- `results` (array)
- `total`

### `get_channels` (~189 tokens)

Channel profiles & metrics

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.

Input parameters:

- `channels` (array, required): 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

Output parameters:

- `channels` (array)
- `unresolved` (array): Requested entries no row answered to; comparison branch only

### `get_channel_timeline` (~122 tokens)

Channel timeline events

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.

Input parameters:

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

Output parameters:

- `channel` (string)
- `events` (array)
- `page`
- `total`

### `get_similar_channels` (~60 tokens)

Similar channels

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

Input parameters:

- `channel` (string, required): Channel slug (Telegram username, without the @) or numeric channel id
- `limit` (integer)

Output parameters:

- `channel` (string)
- `results` (array)

### `get_channel_posts` (~208 tokens)

Posts from a channel

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.

Input parameters:

- `channel` (string, required): Channel slug (Telegram username, without the @) or numeric channel id
- `limit` (integer)
- `message_type` (string): Filter by message type: TEXT, PHOTO, VIDEO, AUDIO, DOCUMENT, UNSUPPORTED (case-insensitive)
- `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

Output parameters:

- `channel` (string)
- `chat_id` (number)
- `posts` (array)

### `get_post_stats` (~170 tokens)

Interaction history of a post

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.

Input parameters:

- `bucket` (string): Series resolution: one snapshot per hour (1h) or day (1d)
- `channel` (string, required): Channel slug (Telegram username, without the @) or numeric channel id
- `message_id` (integer, required): 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

Output parameters:

- `bucket` (string)
- `channel` (string)
- `chat_id` (number)
- `message_id` (number)
- `snapshots` (array): Sparse, oldest first; empty for an untracked post

### `search` (~45 tokens)

Search Statiko

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

Input parameters:

- `query` (string, required): Free-text search query

Output parameters:

- `results` (array)

### `fetch` (~63 tokens)

Fetch a Statiko document

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

Input parameters:

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

Output parameters:

- `id` (string)
- `metadata` (object)
- `text` (string)
- `title` (string)
- `url` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-statiko-telegram/mcp#diagnostics

## Score history

- 2026-09-20: 80
- 2026-09-19: 80
- 2026-09-18: 79
- 2026-09-17: 79
- 2026-09-16: 78
- 2026-09-15: 78
- 2026-09-14: 77
- 2026-09-13: 77

## Common questions

### What is the Statiko — Telegram trends & channel analytics MCP server?

Statiko — Telegram trends & channel analytics is an MCP server listed in the public MCP registry as io.statiko/telegram. Live Telegram data: trending topics, channel profiles & metrics, post history incl. edits/deletions. This page covers its hosted endpoint (https://mcp.statiko.io/mcp).

### Is the Statiko — Telegram trends & channel analytics MCP server safe to use?

Statiko — Telegram trends & channel analytics scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Statiko — Telegram trends & channel analytics MCP server expose?

Statiko — Telegram trends & channel analytics exposes 10 tools: get_trending_topics, get_trend_samples, search_channels, get_channels, get_channel_timeline, and 5 more. Their descriptions and schemas cost roughly 1,255 tokens of context every time the server is loaded.

### Does the Statiko — Telegram trends & channel analytics MCP server require authentication?

Yes. Statiko — Telegram trends & channel analytics asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Statiko — Telegram trends & channel analytics MCP server still maintained?

Statiko — Telegram trends & channel analytics is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.statiko.io/mcp
- Website: https://statiko.io/product/mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-statiko-telegram/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-statiko-telegram/mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-statiko-telegram/mcp