Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
Statiko — Telegram trends & channel analytics is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
10
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Live Telegram data: trending topics, channel profiles & metrics, post history incl. edits/deletions.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http statiko-telegram-trends-channel-analytics-mcp https://mcp.statiko.io/mcp
# 2 — ask your agent for something these tools do
# get_trending_topics, get_trend_samples, search_channels and 7 more
Statiko — Telegram trends & channel analytics costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
STAll 1 server
statiko1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http statiko-telegram-trends-channel-analytics-mcp https://mcp.statiko.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| window | string | no | Rolling 24h window to rank: 'now' (live) or 'yesterday' |
| lang | string | no | ISO-639-1 language code of the board, defaulting to 'ru'. Boards are per-language; pick the language the audience posts in. |
| limit | integer | no | Number of stories to return |
Sample Telegram posts that mention a trending topic, for reading what a story on the trending board is actually about.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| norm | string | yes | Normalized topic key of the story ('norm' field from get_trending_topics) |
| window | string | no | — |
| lang | string | no | ISO-639-1 language code of the board, defaulting to 'ru'. Boards are per-language; pick the language the audience posts in. |
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Channel name or username to match; omit to browse by filters |
| verified | boolean | no | true = verified channels only, false = unverified only |
| categories | array | no | Category slugs to filter by; a channel matching any one passes |
| languages | array | no | ISO-639-1 language codes to filter by (any match) |
| activity | array | no | Last-post activity buckets to filter by (any match) |
| sort | string | no | Sort order: 'subs' (largest first, default) or 'name' |
| limit | integer | no | — |
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;
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. |
| start_date | string | no | Metrics window start (YYYY-MM-DD, inclusive); default -30d. Single channel only |
| end_date | string | no | Metrics window end (YYYY-MM-DD, inclusive); default today. Single channel 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| channel | string | yes | Channel slug (Telegram username, without the @) or numeric channel id |
| event_types | array | no | Event types to keep; omit for all of them |
| order | string | no | Sort by event time: desc (newest first) or asc |
| page | integer | no | — |
| limit | integer | no | — |
Channels that resemble the given one by category and audience — the peer cohort to compare a channel's metrics against.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| channel | string | yes | Channel slug (Telegram username, without the @) or numeric channel id |
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| channel | string | yes | Channel slug (Telegram username, without the @) or numeric channel id |
| query | string | no | Only posts whose text contains this term (case-insensitive substring) |
| since | string | no | Only posts at or after this ISO 8601 timestamp |
| until | string | no | Only posts before this ISO 8601 timestamp |
| message_type | string | no | Filter by message type: TEXT, PHOTO, VIDEO, AUDIO, DOCUMENT, UNSUPPORTED (case-insensitive) |
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| channel | string | yes | Channel slug (Telegram username, without the @) or numeric channel id |
| message_id | integer | yes | Post id within the channel |
| since | string | no | Only snapshots taken at or after this ISO 8601 timestamp |
| until | string | no | Only snapshots taken before this ISO 8601 timestamp |
| bucket | string | no | Series resolution: one snapshot per hour (1h) or day (1d) |
Search Statiko for tracked Telegram channels and currently trending stories. Returns document ids for the fetch tool; results cite statiko.io pages.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free-text search query |
Fetch the full document behind a search result id: a channel profile with metrics, or a trending story with context and sample posts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Document id from a previous search: 'channel:<slug>' or 'trend:<window>:<lang>:<norm>' |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Statiko — Telegram trends & channel analytics or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Statiko — Telegram trends & channel analytics can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.