Limzo Telegram Group Stats
REMOTE · LIMZO.COM · 2 COMPONENTS · SCANNED AUG 3
Read-only public Telegram group stats from Limzo: leaderboards, activity, levels. No API key.
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 →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · limzo.com
claude mcp add --transport http com-limzo-telegram-group-stats https://limzo.com/api/public/mcp
[mcp_servers.com-limzo-telegram-group-stats] url = "https://limzo.com/api/public/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-limzo-telegram-group-stats": {
"type": "remote",
"url": "https://limzo.com/api/public/mcp",
"enabled": true
}
}
} openclaw mcp add com-limzo-telegram-group-stats --url https://limzo.com/api/public/mcp --transport streamable-http
mcp_servers:
com-limzo-telegram-group-stats:
url: "https://limzo.com/api/public/mcp" {
"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.
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.
- 3 Aug 26 +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.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 63
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 3 Aug 2026 · Probed https://limzo.com/api/public/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=limzo.com | CN=WE1,O=Google Trust Services,C=US | 29 Jun 2026 | 27 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | da70d8b9c3cccf6130cb0586fb5336b |
| SANs: limzo.com, *.limzo.com | ||||||
| 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 |
DNSSEC insecure
Validation of limzo.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| limzo.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | frame-ancestors 'self' https://*.telegram.org |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://limzo.com/api/public/mcp | Verified | 200 | |
| http (plaintext) | http://limzo.com/api/public/mcp | HTTPS enforced | 301 | https://limzo.com/api/public/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.
get_global_stats Get network-wide Limzo totals ~66
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| docs | string | — | Human-readable API documentation. |
| ok | boolean | yes | — |
| openapi | string | — | Machine-readable OpenAPI document for the REST API. |
| stats | object | yes | — |
| top_groups | array | — | Current top public groups by Limzo Score. |
No examples provided.
get_group_stats Get public stats for one Telegram group ~239
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.
| Name | Type | Req | Description |
|---|---|---|---|
| range | string | — | Stats window. Defaults to 7d. 30d/all require the group's paid plan; free groups silently fall back to 7d. |
| slug | string | yes | The group's public slug — the last part of its limzo.com/s/<slug> URL. |
| Name | Type | Req | Description |
|---|---|---|---|
| docs | string | — | Human-readable API documentation. |
| generated_at | string | yes | — |
| group | object | yes | — |
| ok | boolean | yes | — |
| openapi | string | — | Machine-readable OpenAPI document for the REST API. |
| range | object | yes | The range actually served — compare `key` with what you requested to detect the plan fallback. |
| schema | string | yes | — |
| stats | object | yes | — |
No examples provided.
list_groups List or search public Telegram groups ~277
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| docs | string | — | Human-readable API documentation. |
| groups | array | yes | — |
| lang | string|null | — | The applied ISO 639-1 language filter, or null when not filtering by language. |
| ok | boolean | yes | — |
| 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 | yes | Groups that matched, before the limit was applied. |
No examples provided.