tgboard — Telegram Directory
REMOTE · TGBOARD.COM
Search 100k+ auto-verified Telegram channels, bots and groups: full-text search and top rankings.
Available components
Last scanned (5 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
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 4 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 Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 472 tokens (~118/item across 4 items; 4 tools + 0 resources), lean.Pass
- 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 Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 23 Oct 26 +1
- Stability: 0.97 → pass security
- 22 Oct 26 −1
- Stability: pass → 0.97 functional
- 19 Oct 26 +1
- Stability: 0.97 → pass security
- 18 Oct 26 −1
- Stability: pass → 0.97 functional
- 28 Sept 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
- 25 Sept 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
- 23 Sept 26 0
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Tool “get_telegram_resource” rewrote its description, which is the text the model reads security
- Tool “search_telegram” rewrote its description, which is the text the model reads security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 22 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ 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 5 Nov 2026 · Probed https://tgboard.com/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tgboard.com | CN=WE1,O=Google Trust Services,C=US | 13 Oct 2026 | 11 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b31c4411211060910e5b17dda6201cae |
| SANs: tgboard.com, *.tgboard.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 tgboard.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| tgboard.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; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://telegram.org https://mc.yandex.ru https://www.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://mc.yandex.ru https://mc.yandex.com https://www.google-analytics.com; font-src 'self' data:; connect-src 'self' https://mc.yandex.ru https://mc.yandex.com wss://mc.yandex.com https://www.google-analytics.com https://region1.google-analytics.com; frame-src https://oauth.telegram.org https://mc.yandex.com; frame-ancestors 'self'; base-uri 'self'; form-action 'self'; require-trusted-types-for 'script'; trusted-types default nextjs#bundler |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tgboard.com/mcp/ | Verified | 200 | |
| http (plaintext) | http://tgboard.com/mcp/ | HTTPS enforced | 301 | https://tgboard.com/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_telegram_resource ~77
Detailed card of one catalog resource by its TGBoard slug. Args: slug: The resource slug from a TGBoard URL or a search result. lang: Description language: en | ru | it | es | fr | ar (default en).
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| slug | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_telegram_categories ~78
Catalog categories with live resource counts (use slugs in other tools). Args: type: Optional filter — channels | bots | apps | groups | stickers. lang: Category-name language: en | ru | it | es | fr | ar (default en).
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| type | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_telegram ~117
Full-text search across the TGBoard catalog of Telegram resources. Args: query: What to look for (topic, name, keyword). type: Optional filter — channels | bots | apps | groups | stickers. lang: Result language: en | ru | it | es | fr | ar (default en). limit: Max results, 1-25 (default 10).
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| limit | integer | – | – |
| query | string | yes | – |
| type | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
top_telegram_resources ~126
The most-followed Telegram resources, optionally within one category. Args: type: channels | bots | apps | groups | stickers (default channels). category: Optional category slug, e.g. 'channels-crypto' (see list_telegram_categories). lang: Result language: en | ru | it | es | fr | ar (default en). limit: Max results, 1-25 (default 10).
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| lang | string | – | – |
| limit | integer | – | – |
| type | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the tgboard — Telegram Directory MCP server?
tgboard — Telegram Directory is a hosted endpoint at https://tgboard.com/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 · tgboard.com
claude mcp add --transport http com-tgboard-catalog 'https://tgboard.com/mcp/'
What is the tgboard — Telegram Directory MCP server?
tgboard — Telegram Directory is an MCP server listed in the public MCP registry as com.tgboard/catalog. Search 100k+ auto-verified Telegram channels, bots and groups: full-text search and top rankings. This page covers its hosted endpoint (https://tgboard.com/mcp/).
Is the tgboard — Telegram Directory MCP server safe to use?
tgboard — Telegram Directory scores 80 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 tgboard — Telegram Directory MCP server expose?
tgboard — Telegram Directory exposes 4 tools: search_telegram, top_telegram_resources, get_telegram_resource, list_telegram_categories. Their descriptions and schemas cost roughly 398 tokens of context every time the server is loaded.
Does the tgboard — Telegram Directory MCP server require authentication?
No. We connected to tgboard — Telegram Directory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the tgboard — Telegram Directory MCP server still maintained?
tgboard — Telegram Directory is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.