Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.

Is statiko free to use?

Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.

What tools does statiko have?

10 tools: get_channel_posts, get_post_stats, get_similar_channels, search_channels, get_trending_topics, get_channels, get_trend_samples, search, ….

Is statiko safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

_ registry / mcp http-sse · checked 3h ago

statiko

https://mcp.statiko.io

Registry code: 63f0608e04a7df46

api record

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

from a public catalogue that lists it, not from the operator

endpoint: https://mcp.statiko.io/mcp
protocol: http-sse ·2025-06-18
authentication: none observed
public key: none — nobody has proven they own this listing · is it yours? claim it
karma: 0 · newcomer

_ is it live, free and safe measured by this hub

Is statiko live?: Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
Is statiko free to use?: Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does statiko have?: 10 tools: get_channel_posts, get_post_stats, get_similar_channels, search_channels, get_trending_topics, get_channels, get_trend_samples, search, ….
Is statiko safe to connect?: The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

reachable

live

uptime, 30 days

98.8%

90 days 98.8%· all time 98.8%

latency

445ms

last good check

priced tools

of 10 tools

_ answered our checks, 90 days 414 checks · signed record

2026-11-13 20:48 degraded → live
2026-11-13 09:02 live → degraded· timeout after 20000ms
2026-10-20 23:08 degraded → live
2026-10-20 21:51 live → degraded· timeout after 20000ms
2026-10-20 14:07 degraded → live

_ what it is for

topic: communication social media
used for: get trending telegram topics
get a telegram channel profile
get posts from a telegram channel
track a post's view stats
find similar telegram channels
takes → gives: text → data
tools: 10 reads

_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 10 tools

10 auth-required 10 of 10 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

get_channel_posts reads auth-required never probed

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.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "channel"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 50,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "maxLength": 500,
      "minLength": 1,
      "description": "Only posts whose text contains this term (case-insensitive substring)"
    },
    "since": {
      "type": "string",
      "description": "Only posts at or after this ISO 8601 timestamp"
    },
    "until": {
      "type": "string",
      "description": "Only posts before this ISO 8601 timestamp"
    },
    "channel": {
      "type": "string",
      "minLength": 1,
      "description": "Channel slug (Telegram username, without the @) or numeric channel id"
    },
    "message_type": {
      "type": "string",
      "description": "Filter by message type: TEXT, PHOTO, VIDEO, AUDIO, DOCUMENT, UNSUPPORTED (case-insensitive)"
    }
  }
}

arguments 38 lines

get_post_stats reads auth-required never probed

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.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "channel",
    "message_id"
  ],
  "properties": {
    "since": {
      "type": "string",
      "description": "Only snapshots taken at or after this ISO 8601 timestamp"
    },
    "until": {
      "type": "string",
      "description": "Only snapshots taken before this ISO 8601 timestamp"
    },
    "bucket": {
      "enum": [
        "1h",
        "1d"
      ],
      "type": "string",
      "default": "1h",
      "description": "Series resolution: one snapshot per hour (1h) or day (1d)"
    },
    "channel": {
      "type": "string",
      "minLength": 1,
      "description": "Channel slug (Telegram username, without the @) or numeric channel id"
    },
    "message_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "Post id within the channel"
    }
  }
}

arguments 38 lines

get_similar_channels reads auth-required 11h ago

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

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "channel"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 20,
      "minimum": 1
    },
    "channel": {
      "type": "string",
      "minLength": 1,
      "description": "Channel slug (Telegram username, without the @) or numeric channel id"
    }
  }
}

arguments 20 lines

search_channels reads auth-required 3h ago

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.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "sort": {
      "enum": [
        "subs",
        "name"
      ],
      "type": "string",
      "description": "Sort order: 'subs' (largest first, default) or 'name'"
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 20,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "minLength": 1,
      "description": "Channel name or username to match; omit to browse by filters"
    },
    "activity": {
      "type": "array",
      "items": {
        "enum": [
          "recently",
          "week",
          "month",
          "dormant",
          "inactive"
        ],
        "type": "string"
      },
      "description": "Last-post activity buckets to filter by (any match)"
    },
    "verified": {
      "type": "boolean",
      "description": "true = verified channels only, false = unverified only"
    },
    "languages": {
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1
      },
      "description": "ISO-639-1 language codes to filter by (any match)"
    },
    "categories": {
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1
      },
      "description": "Category slugs to filter by; a channel matching any one passes"
    }
  }
}

arguments 59 lines

get_trending_topics reads auth-required 3h ago

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.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "lang": {
      "type": "string",
      "default": "ru",
      "description": "ISO-639-1 language code of the board, defaulting to 'ru'. Boards are per-language; pick the language the audience posts in."
    },
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 50,
      "minimum": 1,
      "description": "Number of stories to return"
    },
    "window": {
      "enum": [
        "now",
        "yesterday"
      ],
      "type": "string",
      "default": "now",
      "description": "Rolling 24h window to rank: 'now' (live) or 'yesterday'"
    }
  }
}

arguments 27 lines

get_channels reads auth-required 31h ago

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.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "channels"
  ],
  "properties": {
    "channels": {
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1
      },
      "maxItems": 10,
      "minItems": 1,
      "description": "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": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Metrics window end (YYYY-MM-DD, inclusive); default today. Single channel only"
    },
    "start_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Metrics window start (YYYY-MM-DD, inclusive); default -30d. Single channel only"
    }
  }
}

arguments 29 lines

get_trend_samples reads auth-required 11h ago

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

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "norm"
  ],
  "properties": {
    "lang": {
      "type": "string",
      "default": "ru",
      "description": "ISO-639-1 language code of the board, defaulting to 'ru'. Boards are per-language; pick the language the audience posts in."
    },
    "norm": {
      "type": "string",
      "minLength": 1,
      "description": "Normalized topic key of the story ('norm' field from get_trending_topics)"
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 20,
      "minimum": 1
    },
    "window": {
      "enum": [
        "now",
        "yesterday"
      ],
      "type": "string",
      "default": "now"
    }
  }
}

arguments 33 lines

search reads auth-required 3h ago

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

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "minLength": 1,
      "description": "Free-text search query"
    }
  }
}

arguments 14 lines

fetch reads auth-required 3d ago

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

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1,
      "description": "Document id from a previous search: 'channel:<slug>' or 'trend:<window>:<lang>:<norm>'"
    }
  }
}

arguments 14 lines

get_channel_timeline reads auth-required 11h ago

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.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "channel"
  ],
  "properties": {
    "page": {
      "type": "integer",
      "default": 0,
      "maximum": 9007199254740991,
      "minimum": 0
    },
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 50,
      "minimum": 1
    },
    "order": {
      "enum": [
        "asc",
        "desc"
      ],
      "type": "string",
      "default": "desc",
      "description": "Sort by event time: desc (newest first) or asc"
    },
    "channel": {
      "type": "string",
      "minLength": 1,
      "description": "Channel slug (Telegram username, without the @) or numeric channel id"
    },
    "event_types": {
      "type": "array",
      "items": {
        "enum": [
          "CHANNEL_FOLLOWED",
          "CHANNEL_TITLE_CHANGED",
          "CHANNEL_ABOUT_CHANGED",
          "CHANNEL_PHOTO_CHANGED",
          "VERIFIED_STATUS_CHANGED",
          "SUBSCRIBERS_MILESTONE",
          "CHANNEL_FIRST_MESSAGE",
          "POST_EDITED",
          "POST_DELETED",
          "VIEW_MILESTONE",
          "COMMENT_MILESTONE"
        ],
        "type": "string"
      },
      "description": "Event types to keep; omit for all of them"
    }
  }
}

arguments 55 lines

_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 63f0608e04a7df46.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/63f0608e04a7df46/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/63f0608e04a7df46/badge.svg)](https://brick.blue/agent/63f0608e04a7df46?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know

card completeness

100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

paid reviews: 0
positive: 0
negative: 0
score: —

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.