Limzo Telegram Group Stats
REMOTE · LIMZO.COM · 2 COMPONENTS · SCANNED SEP 20
Read-only stats for public Telegram groups tracked by Limzo, the anti-spam bot. 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 → Why this is hard to 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 Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 738 tokens (~246/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Limzo Telegram Group Stats MCP server?
Limzo Telegram Group Stats is a hosted endpoint at https://limzo.com/api/public/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · limzo.com
claude mcp add --transport http com-limzo-telegram-group-stats 'https://limzo.com/api/public/mcp'
{
"mcpServers": {
"com-limzo-telegram-group-stats": {
"url": "https://limzo.com/api/public/mcp"
}
}
} {
"servers": {
"com-limzo-telegram-group-stats": {
"type": "http",
"url": "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": {
"Transport": "http",
"Url": "https://limzo.com/api/public/mcp"
}
}
} assistant mcp add com-limzo-telegram-group-stats -t streamable-http -u '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.
- 27 Aug 26 0
- Tool “get_group_stats” rewrote its description, which is the text the model reads security
- Tool “list_groups” rewrote its description, which is the text the model reads security
- Schema quality: 223 → 246 ▼ functional
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 6 Aug 26 0
- Tool “get_global_stats” rewrote its description, which is the text the model reads security
- 31 Jul 26 0
- 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 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 20 Sept 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 | 27 Aug 2026 | 25 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 73527a8869da4fe0139c6610a7e9f777 |
| 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_global_stats Get network-wide Limzo totals ~81
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 durable lifetime totals (messages analyzed, members tracked, spam messages removed) and 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 ~277
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. For a private group (one with no public t.me handle) the member identities, the group description and member_count are withheld too: aggregates plus an anonymised leaderboard are all it returns.
| 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 ~306
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. The directory covers PUBLIC groups only — a group with no t.me handle is never listed, though it may still have a /s/ page. 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.
What is the Limzo Telegram Group Stats MCP server?
Limzo Telegram Group Stats is an MCP server listed in the public MCP registry as com.limzo/telegram-group-stats. Read-only stats for public Telegram groups tracked by Limzo, the anti-spam bot. No API key. This page covers its hosted endpoint (https://limzo.com/api/public/mcp).
Is the Limzo Telegram Group Stats MCP server safe to use?
Limzo Telegram Group Stats scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Limzo Telegram Group Stats MCP server expose?
Limzo Telegram Group Stats exposes 3 tools: get_group_stats, list_groups, get_global_stats. Their descriptions and schemas cost roughly 664 tokens of context every time the server is loaded.
Does the Limzo Telegram Group Stats MCP server require authentication?
No. We connected to Limzo Telegram Group Stats without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Limzo Telegram Group Stats MCP server still maintained?
Limzo Telegram Group Stats is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.