Statiko — Telegram trends & channel analytics
REMOTE · MCP.STATIKO.IO · SCANNED SEP 20
Live Telegram data: trending topics, channel profiles & metrics, post history incl. edits/deletions.
Available components
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. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 81% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · mcp.statiko.io
claude mcp add --transport http io-statiko-telegram 'https://mcp.statiko.io/mcp'
{
"mcpServers": {
"io-statiko-telegram": {
"url": "https://mcp.statiko.io/mcp"
}
}
} {
"servers": {
"io-statiko-telegram": {
"type": "http",
"url": "https://mcp.statiko.io/mcp"
}
}
} [mcp_servers.io-statiko-telegram] url = "https://mcp.statiko.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-statiko-telegram": {
"type": "remote",
"url": "https://mcp.statiko.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-statiko-telegram --url 'https://mcp.statiko.io/mcp' --transport streamable-http
mcp_servers:
io-statiko-telegram:
url: "https://mcp.statiko.io/mcp" {
"McpServers": {
"io-statiko-telegram": {
"Transport": "http",
"Url": "https://mcp.statiko.io/mcp"
}
}
} assistant mcp add io-statiko-telegram -t streamable-http -u 'https://mcp.statiko.io/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 14 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Sept 26 77
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.statiko.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=statiko.io | CN=WE1,O=Google Trust Services,C=US | 22 Aug 2026 | 20 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | acfd6bb99b8d785413a3083234b62a1c |
| SANs: statiko.io, mcp.statiko.io, *.mcp.statiko.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.statiko.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| statiko.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="Missing Authorization header", scope="mcp:read", resource_metadata="https://mcp.statiko.io/.well-known/oauth-protected-resource/mcp"
Bearer error="invalid_token", error_description="Missing Authorization header", scope="mcp:read", resource_metadata="https://mcp.statiko.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://mcp.statiko.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.statiko.io/mcp |
| Authorisation server | https://statiko.io/api/auth |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.statiko.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.statiko.io/mcp | HTTPS enforced | 301 | https://mcp.statiko.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fetch Fetch a Statiko document ~63
Fetch the full document behind a search result id: a channel profile with metrics, or a trending story with context and sample posts.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Document id from a previous search: 'channel:<slug>' or 'trend:<window>:<lang>:<norm>' |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| metadata | object | yes | – |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
get_channel_posts Posts from a channel ~208
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.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | – |
| chat_id | number | yes | – |
| posts | array | yes | – |
No examples provided.
get_channel_timeline Channel timeline events ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | 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 | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | – |
| events | array | yes | – |
| page | – | – | – |
| total | – | – | – |
No examples provided.
get_channels Channel profiles & metrics ~189
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.
| Name | Type | Req | Description |
|---|---|---|---|
| channels | array | yes | 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| channels | array | yes | – |
| unresolved | array | – | Requested entries no row answered to; comparison branch only |
No examples provided.
get_post_stats Interaction history of a post ~170
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | – | Series resolution: one snapshot per hour (1h) or day (1d) |
| channel | string | yes | Channel slug (Telegram username, without the @) or numeric channel id |
| message_id | integer | yes | 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | yes | – |
| channel | string | yes | – |
| chat_id | number | yes | – |
| message_id | number | yes | – |
| snapshots | array | yes | Sparse, oldest first; empty for an untracked post |
No examples provided.
get_similar_channels Similar channels ~60
Channels that resemble the given one by category and audience — the peer cohort to compare a channel's metrics against.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | Channel slug (Telegram username, without the @) or numeric channel id |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | – |
| results | array | yes | – |
No examples provided.
get_trend_samples Posts behind a trend ~105
Sample Telegram posts that mention a trending topic, for reading what a story on the trending board is actually about.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Normalized topic key of the story ('norm' field from get_trending_topics) |
| window | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | yes | – |
| norm | string | yes | – |
| samples | array | yes | – |
| window | string | yes | – |
No examples provided.
get_trending_topics Trending topics board ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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' |
| Name | Type | Req | Description |
|---|---|---|---|
| computed_at | – | – | – |
| items | array | yes | – |
| lang | string | yes | – |
| languages | – | – | – |
| url | string | yes | – |
| window | string | yes | – |
| window_end | – | – | – |
| window_start | – | – | – |
No examples provided.
search Search Statiko ~45
Search Statiko for tracked Telegram channels and currently trending stories. Returns document ids for the fetch tool; results cite statiko.io pages.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Free-text search query |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
search_channels Search Telegram channels ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
| total | – | – | – |
No examples provided.
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.