# Limzo Telegram Group Stats (remote · limzo.com)

Read-only public Telegram group stats from Limzo: leaderboards, activity, levels. No API key.

- Trust score: 66/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `limzo.com`: 66/100 (this document), [markdown](https://verifymcp.io/servers/com-limzo-telegram-group-stats/api-public-mcp.md), [page](https://verifymcp.io/servers/com-limzo-telegram-group-stats/api-public-mcp)
- npm · `limzo-mcp`: 30/100, [markdown](https://verifymcp.io/servers/com-limzo-telegram-group-stats/limzo-mcp.md), [page](https://verifymcp.io/servers/com-limzo-telegram-group-stats/limzo-mcp)

## Channel facts

- Endpoint: `https://limzo.com/api/public/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.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-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 656 tokens (~218/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-limzo-telegram-group-stats https://limzo.com/api/public/mcp
```

### Codex

```toml
[mcp_servers.com-limzo-telegram-group-stats]
url = "https://limzo.com/api/public/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-limzo-telegram-group-stats": {
      "type": "remote",
      "url": "https://limzo.com/api/public/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-limzo-telegram-group-stats --url https://limzo.com/api/public/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-limzo-telegram-group-stats:
    url: "https://limzo.com/api/public/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-limzo-telegram-group-stats": {
      "type": "http",
      "url": "https://limzo.com/api/public/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-08-03 (score 66, +1)

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

### 2026-07-31 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 64, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 65, +1)

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

### 2026-07-27 (score 64, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 63)

First indexed and scored.

## MCP tools (3)

### `get_group_stats` (~239 tokens)

Get public stats for one Telegram group

Call this when the user asks about the activity, health, leaderboard, mood, or trends of a specific Telegram group tracked by Limzo. `slug` is the last part of the group's public page URL, limzo.com/s/<slug> (e.g. "hipo"). Returns the curated limzo.public_stats/v1 JSON: messages, replies, active members, daily series, top members, mood, reactions, language mix, the Limzo Levels ladder (lifetime XP + badge tiers), and weekly-league standings when the group has the league enabled. Optional `range`: 7d (default), 30d, all — the wider ranges only serve real data for groups on a paid plan and otherwise silently fall back to 7d, so check `range.key` in the result. Never includes verbatim member messages.

Input parameters:

- `range` (string): Stats window. Defaults to 7d. 30d/all require the group's paid plan; free groups silently fall back to 7d.
- `slug` (string, required): The group's public slug — the last part of its limzo.com/s/<slug> URL.

Output parameters:

- `docs` (string): Human-readable API documentation.
- `generated_at` (string)
- `group` (object)
- `ok` (boolean)
- `openapi` (string): Machine-readable OpenAPI document for the REST API.
- `range` (object): The range actually served — compare `key` with what you requested to detect the plan fallback.
- `schema` (string)
- `stats` (object)

### `list_groups` (~277 tokens)

List or search public Telegram groups

Call this to discover Telegram groups tracked by Limzo — to browse the directory, filter by language, or find a group's slug for get_group_stats. Optional `query` filters case-insensitively over group title, username, slug, and description. Optional `lang` (ISO 639-1, e.g. "fa", "es") keeps only groups where that language is a meaningful share of what members write — the way to answer "find active Persian/Spanish groups". Omit both to list the top groups by Limzo Score. Each row carries a `language` mix (primary language + top languages as percentages); rows also include slug, title, username, plan, member_count, 7-day messages and active members, score and page URLs, plus `total_matches` so you can tell when more groups matched than were returned.

Input parameters:

- `lang` (string): ISO 639-1 language code (e.g. "fa", "es", "en"). Keeps only groups where that language is a meaningful share of the group.
- `limit` (integer): Maximum groups to return. Defaults to 20, capped at 50.
- `query` (string): Keyword matched case-insensitively against group title, username, slug, and description. Omit to list the top groups by Limzo Score.

Output parameters:

- `docs` (string): Human-readable API documentation.
- `groups` (array)
- `lang` (string|null): The applied ISO 639-1 language filter, or null when not filtering by language.
- `ok` (boolean)
- `openapi` (string): Machine-readable OpenAPI document for the REST API.
- `query` (string|null): The normalized search keyword, or null when listing top groups.
- `total_matches` (integer): Groups that matched, before the limit was applied.

### `get_global_stats` (~66 tokens)

Get network-wide Limzo totals

Call this for network-wide numbers across all public Telegram groups tracked by Limzo (group count, messages, active users, replies, reactions, karma — 7-day and all-time) plus the current top groups by Limzo Score. For finding a specific group, prefer list_groups.

Output parameters:

- `docs` (string): Human-readable API documentation.
- `ok` (boolean)
- `openapi` (string): Machine-readable OpenAPI document for the REST API.
- `stats` (object)
- `top_groups` (array): Current top public groups by Limzo Score.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-limzo-telegram-group-stats/api-public-mcp#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 65
- 2026-08-01: 65
- 2026-07-31: 65
- 2026-07-30: 64
- 2026-07-29: 65
- 2026-07-28: 64
- 2026-07-27: 64
- 2026-07-26: 63

## Links

- Remote endpoint: https://limzo.com/api/public/mcp
- Website: https://limzo.com/docs/
- Changelog RSS feed: https://verifymcp.io/servers/com-limzo-telegram-group-stats/api-public-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-limzo-telegram-group-stats/api-public-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-limzo-telegram-group-stats/api-public-mcp