// SCAN REPORT

Tgstat

16 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 29 Jun 2026

0 can modify or destroy data

16 read-only

16 tools total

Community server · catalogue entry verified 29/06/2026

How to control Tgstat ↓

TOOL MAP

What Tgstat exposes to your agents

Read (16) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control Tgstat

PolicyLayer is an MCP gateway — it sits between your AI agents and Tgstat, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "compare_channels": {
    "limits": [
      {
        "counter": "compare_channels_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Tgstat — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON TGSTAT →

Instant setup, no code required.

FULL CATALOGUE

All 16 Tgstat tools

READ 16 tools

Read compare_channels Compare several channels side by side on subscribers, average reach and ERR (one channels/stat lookup per chan Read get_channel Get a Telegram channel Read get_channel_forwards Posts from other channels that forwarded this channel Read get_channel_mentions Find where a channel is mentioned or forwarded by other channels and chats. Read get_channel_posts Get recent posts of a channel with view metrics. Supports an optional date range and pagination. Read get_channel_stats Get a channel Read get_post Get details of a single post: views, forwards, reactions, text. Read get_post_stats Get a post Read get_usage Show your TGStat API usage and quota: requests / channels / words spent vs allowed, and package expiry. Read get_word_mentions Track how often a keyword is mentioned across Telegram over time (mentions + views per period). Read get_word_mentions_by_channels Break down keyword mentions by the channels that mention it most (channel + mention/view counts). Read list_countries List available country codes (use as the Read list_languages List available language codes (use as the Read search_channels Search Telegram channels by query, with optional category / language / country / type filters. Returns curated Read search_posts Full-text search across Telegram posts, with optional source-type / category / language / country / date filte

FAQ

Questions about Tgstat

Is the Tgstat MCP server safe to use without restrictions? +

The Tgstat server is primarily read-only with 16 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Tgstat MCP server expose? +

16 tools across 1 categories: Read. 16 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on Tgstat? +

Register the Tgstat MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Tgstat tool call.

Deterministic rules across all 16 Tgstat tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON TGSTAT →

Instant setup, no code required.

16 Tgstat tools catalogued and risk-classified — across an index of 43,000+ MCP servers.