io.github.leshchenko1979/fast-mcp-telegram
REMOTE · TG-MCP.L1979.RU · 2 COMPONENTS · SCANNED AUG 4
Multi-tenant Telegram gateway for AI agents — HTTP+stdio, 8 tools, MTProto User API
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (send_message). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability52
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2703 tokens (~337/item across 8 items; 8 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 Management30
- Stability observed for 9 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 · tg-mcp.l1979.ru
claude mcp add --transport http leshchenko1979-fast-mcp-telegram https://tg-mcp.l1979.ru/v1/mcp
[mcp_servers.leshchenko1979-fast-mcp-telegram] url = "https://tg-mcp.l1979.ru/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"leshchenko1979-fast-mcp-telegram": {
"type": "remote",
"url": "https://tg-mcp.l1979.ru/v1/mcp",
"enabled": true
}
}
} openclaw mcp add leshchenko1979-fast-mcp-telegram --url https://tg-mcp.l1979.ru/v1/mcp --transport streamable-http
mcp_servers:
leshchenko1979-fast-mcp-telegram:
url: "https://tg-mcp.l1979.ru/v1/mcp" {
"mcpServers": {
"leshchenko1979-fast-mcp-telegram": {
"type": "http",
"url": "https://tg-mcp.l1979.ru/v1/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.
- 4 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 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
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Jul 26 0
- Tool “send_message_to_phone” rewrote its description, which is the text the model reads security
- Tool “edit_message” rewrote its description, which is the text the model reads security
- Tool “send_message” rewrote its description, which is the text the model reads security
- “send_message_to_phone” reworded the description of “parse_mode” cosmetic
- “edit_message” reworded the description of “parse_mode” cosmetic
- “send_message” reworded the description of “parse_mode” cosmetic
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 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
- 26 Jul 26 58
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 4 Aug 2026 · Probed https://tg-mcp.l1979.ru/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tg-mcp.l1979.ru | CN=YR2,O=Let's Encrypt,C=US | 11 Jun 2026 | 9 Sept 2026 | RSA 4096 | SHA256-RSA | 5b8a3e858c823f602e67d6d286d19d7e193 |
| SANs: tg-mcp.l1979.ru | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of tg-mcp.l1979.ru. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ru. | present | 51575 | 8 | Verified |
| l1979.ru. | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tg-mcp.l1979.ru/v1/mcp | Verified | 200 | |
| http (plaintext) | http://tg-mcp.l1979.ru/v1/mcp | HTTPS enforced | 301 | https://tg-mcp.l1979.ru/v1/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.
edit_message Edit message ~292
Replace the text of an existing message in a Telegram chat. Only works on messages sent by the authenticated account. Cannot edit media or other message attributes — text only. parse_mode: classic markdown/html/auto or rich (Rich Message; dialect auto-detected). Success: dict with message_id, date, chat, text, status='edited', and edit_date (rich messages also set rich=true and rich_format). Error: dict with ok=false and error string (e.g. message not found or not editable). Use edit_message to update a previously sent message; use send_message to create new ones. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | Target chat: numeric id (e.g. -100…), username without @, or 'me' for Saved Messages. |
| message | string | yes | Message text. When sending files, used as caption. |
| message_id | integer | yes | Message id in this chat to edit (from get_messages or Telegram). |
| parse_mode | string | — | 'markdown'/'html'/'auto': classic entity formatting (auto detects). 'rich': Telegram Rich Message document; dialect auto-detected (known HTML tags outside code → rich HTML, else rich markdown). Defau… |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | — | — |
| chat | object | — | — |
| code | integer | — | — |
| date | string | — | — |
| edit_date | string | — | — |
| error | string | — | — |
| error_code | string | — | — |
| exception | object | — | — |
| message_id | integer | — | — |
| ok | boolean | — | — |
| operation | string | — | — |
| params | object | — | — |
| reply_markup | object | — | — |
| rich | boolean | — | — |
| rich_format | string | — | — |
| sender | object | — | — |
| status | string | — | — |
| text | string | — | — |
| topic_id | integer | — | — |
No examples provided.
find_chats Find chats ~380
Find users/groups/channels by name, username, or phone. Comma-separated usernames are searched in parallel and results are merged round-robin. Global search (query required) searches all Telegram; with min_date, max_date, or filter, search uses dialog list or a named filter; include_peers filters use last-activity from GetPeerDialogs; flag-based filters use dialog list dates. Success: dict with key chats (list of chat objects). Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md
| Name | Type | Req | Description |
|---|---|---|---|
| chat_type | string | — | Comma-separated chat kinds: private, bot, group, channel. Case-insensitive; extra spaces allowed. |
| folder | string | — | Telegram folder name (case-insensitive exact match after normalization). In Telegram's UI these are called folders; internally they are "dialog filters" — saved filter presets that group chats by cus… |
| limit | integer | — | Maximum chats to return (recommended 50 or less). |
| max_date | string | — | Inclusive maximum date filter (ISO 8601 date or datetime). Omit for no upper bound. |
| min_date | string | — | Inclusive minimum date filter (ISO 8601 date or datetime). Omit for no lower bound. |
| public | boolean | — | If true, prefer chats with a public username; if false, without. Does not apply to private DMs. Omit to skip this filter. |
| query | string | — | Name, username (no @), phone (+country…), or comma-separated usernames for batch lookup. Example: 'alice,bob,charlie'. Required for global search unless you use min_date/max_date or folder alone. |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | — | — |
| chats | array | — | — |
| code | integer | — | — |
| error | string | — | — |
| error_code | string | — | — |
| exception | object | — | — |
| ok | boolean | — | — |
| operation | string | — | — |
| params | object | — | — |
No examples provided.
get_chat_info Get chat info ~118
Load profile and metadata for one user, bot, group, or channel. Success: info dict; forum chats may include topics up to topics_limit. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | Target chat: numeric id (e.g. -100…), username without @, or 'me' for Saved Messages. |
| topics_limit | integer | — | Max forum topics to list when the chat is a forum. |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | — | — |
| code | integer | — | — |
| error | string | — | — |
| error_code | string | — | — |
| exception | object | — | — |
| first_name | string | — | — |
| id | integer | — | — |
| is_bot | boolean | — | — |
| is_channel | boolean | — | — |
| is_forum | boolean | — | — |
| is_group | boolean | — | — |
| is_user | boolean | — | — |
| last_name | string | — | — |
| ok | boolean | — | — |
| operation | string | — | — |
| params | object | — | — |
| participants_count | integer | — | — |
| phone | string | — | — |
| title | string | — | — |
| topics | array | — | — |
| topics_has_more | boolean | — | — |
| username | string | — | — |
No examples provided.
get_messages Get messages in chat ~662
Read or search messages in one chat: browse latest, search text, fetch by ids, or load replies to a message (comments, forum topics, threads). Use from_user to filter by sender (server-side, per-chat only). Use context to include neighboring messages and reply chains around each result. Use include_replies to fetch up to 5 direct replies per result. Do not combine message_ids with query or reply_to_id. Success: messages, has_more, optional total_count and discussion fields. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md
| Name | Type | Req | Description |
|---|---|---|---|
| auto_expand_batches | integer | — | Extra search batches to run when filters narrow results. Higher values may return more matches at the cost of latency. |
| chat_id | string | yes | Target chat: numeric id (e.g. -100…), username without @, or 'me' for Saved Messages. |
| context | integer | — | Number of surrounding messages to include as context for each search result. 0 = disabled (default). 1-10 = include N messages before and N after each result. Also fetches the message being replied t… |
| from_user | string | — | Only return messages from this sender. Not a display-name or contact-name search — bare strings resolve like chat_id via get_entity (usernames are case-insensitive and may match an unrelated channel)… |
| include_replies | boolean | — | If true, fetch up to 5 direct replies per search result and attach as replies. Each result costs one API call (not batchable). Default: false. |
| include_total_count | boolean | — | If true, response may include total_count where supported (per-chat search; ignored for global search). |
| limit | integer | — | Maximum messages to return (recommended 50 or less). |
| max_date | string | — | Inclusive maximum date filter (ISO 8601 date or datetime). Omit for no upper bound. |
| message_ids | array | — | Exact message ids to fetch. Mutually exclusive with query and reply_to_id. |
| min_date | string | — | Inclusive minimum date filter (ISO 8601 date or datetime). Omit for no lower bound. |
| query | string | — | Search within this chat only; comma-separated terms. Omit to browse latest or use message_ids / reply_to_id modes. |
| reply_to_id | integer | — | Anchor message id: channel post id, forum topic_id from get_chat_info, or a message id for direct replies. Use with thread_scope. |
| thread_scope | string | — | Only with reply_to_id. auto: full forum topic (topic_id) or channel comment thread via getReplies; else direct replies. full: nested branch under a message id (forum in-topic uses search window, not… |
| Name | Type | Req | Description |
|---|---|---|---|
| _warning | string | — | — |
| action | string | — | — |
| code | integer | — | — |
| error | string | — | — |
| error_code | string | — | — |
| exception | object | — | — |
| has_more | boolean | — | — |
| messages | array | — | — |
| ok | boolean | — | — |
| operation | string | — | — |
| params | object | — | — |
| total_count | integer | — | — |
No examples provided.
invoke_mtproto Invoke MTProto ~187
Low-level Telegram API (MTProto) invoke for methods not wrapped by other tools. Dangerous methods require allow_dangerous=true. Success: API result dict or normalized error. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md
| Name | Type | Req | Description |
|---|---|---|---|
| allow_dangerous | boolean | — | If false, destructive methods (e.g. deletes) are blocked. Set true only when intended. |
| method_full_name | string | yes | Telegram API method, e.g. "messages.GetHistory" or "users.GetFullUser" (normalization applied). |
| params_json | string | yes | JSON object string of TL parameters as in Telegram API docs; nested TL uses "_": "typeName" discriminator. |
| resolve | boolean | — | If true, resolve string/int peer-like fields to TL Input* entities before invoke. |
| Name | Type | Req | Description |
|---|---|---|---|
| _ | string | — | — |
| action | string | — | — |
| chats | array | — | — |
| code | integer | — | — |
| date | integer | — | — |
| error | string | — | — |
| error_code | string | — | — |
| exception | object | — | — |
| id | integer | — | — |
| messages | array | — | — |
| ok | boolean | — | — |
| operation | string | — | — |
| params | object | — | — |
| result | object | — | — |
| users | array | — | — |
No examples provided.
search_messages_globally Search messages globally ~301
Search all Telegram chats at once (not scoped to one chat). Comma-separated query terms; optional filters by date, chat kind, and public username. Success: message list and metadata dict. Global search ignores include_total_count. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md
| Name | Type | Req | Description |
|---|---|---|---|
| auto_expand_batches | integer | — | Extra search batches to run when filters narrow results. Higher values may return more matches at the cost of latency. |
| chat_type | string | — | Comma-separated chat kinds: private, bot, group, channel. Case-insensitive; extra spaces allowed. |
| include_total_count | boolean | — | If true, response may include total_count where supported (per-chat search; ignored for global search). |
| limit | integer | — | Maximum messages to return (recommended 50 or less). |
| max_date | string | — | Inclusive maximum date filter (ISO 8601 date or datetime). Omit for no upper bound. |
| min_date | string | — | Inclusive minimum date filter (ISO 8601 date or datetime). Omit for no lower bound. |
| public | boolean | — | If true, prefer chats with a public username; if false, without. Does not apply to private DMs. Omit to skip this filter. |
| query | string | yes | Search terms, comma-separated for multiple terms (OR-style global search). Required. |
| Name | Type | Req | Description |
|---|---|---|---|
| _warning | string | — | — |
| action | string | — | — |
| code | integer | — | — |
| error | string | — | — |
| error_code | string | — | — |
| exception | object | — | — |
| has_more | boolean | — | — |
| messages | array | — | — |
| ok | boolean | — | — |
| operation | string | — | — |
| params | object | — | — |
| total_count | integer | — | — |
No examples provided.
send_message Send message ~420
Send text and optional file attachments to a Telegram chat. Supports reply-to (including forum topics and channel discussion groups), parse_mode: classic markdown/html/auto (entities) or rich (Rich Message document; dialect auto-detected). parse_mode=rich cannot be combined with files. File attachments as http(s) URLs, local paths, or data: URIs. When files are provided, the message text becomes a caption. For channel posts with reply_to_id, automatically posts in the linked discussion group. Success: dict with message_id, date, chat, text, status='sent', and sender info (rich messages also set rich=true and rich_format). Error: dict with ok=false and error string. Use send_message to create new messages; use edit_message to modify existing ones. Use send_message_to_phone when targeting a phone number instead of a chat_id. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | Target chat: numeric id (e.g. -100…), username without @, or 'me' for Saved Messages. |
| files | array | — | List of attachment URLs, local paths, or data URIs (one or more strings). data: URIs (data:<mime>;base64,<payload>) work in all server modes; local paths work in stdio mode only. |
| message | string | yes | Message text. When sending files, used as caption. |
| parse_mode | string | — | 'markdown'/'html'/'auto': classic entity formatting (auto detects). 'rich': Telegram Rich Message document; dialect auto-detected (known HTML tags outside code → rich HTML, else rich markdown). Defau… |
| reply_to_id | integer | — | Telegram message id to reply to. For forums, topic root id; for channel posts, post id (may create a comment). Omit for a new top-level message. |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | — | — |
| chat | object | — | — |
| code | integer | — | — |
| date | string | — | — |
| edit_date | string | — | — |
| error | string | — | — |
| error_code | string | — | — |
| exception | object | — | — |
| message_id | integer | — | — |
| ok | boolean | — | — |
| operation | string | — | — |
| params | object | — | — |
| reply_markup | object | — | — |
| rich | boolean | — | — |
| rich_format | string | — | — |
| sender | object | — | — |
| status | string | — | — |
| text | string | — | — |
| topic_id | integer | — | — |
No examples provided.
send_message_to_phone Send message to phone ~343
Send to a phone number: may create a temporary contact, then send text or files. Supports parse_mode: classic markdown/html/auto or rich (Rich Message; dialect auto-detected). parse_mode=rich cannot be combined with files. Success: send result plus contact_was_new / contact_removed when applicable. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | — | List of attachment URLs, local paths, or data URIs (one or more strings). data: URIs (data:<mime>;base64,<payload>) work in all server modes; local paths work in stdio mode only. |
| first_name | string | — | First name when creating a temporary contact. |
| last_name | string | — | Last name when creating a temporary contact. |
| message | string | yes | Message text. When sending files, used as caption. |
| parse_mode | string | — | 'markdown'/'html'/'auto': classic entity formatting (auto detects). 'rich': Telegram Rich Message document; dialect auto-detected (known HTML tags outside code → rich HTML, else rich markdown). Defau… |
| phone_number | string | yes | E.164 phone number with country code, e.g. +1234567890 (must be on Telegram). |
| remove_if_new | boolean | — | If true, delete the contact after send when it was created only for this send. |
| reply_to_msg_id | integer | — | Reply to this message id in the target chat after resolve. |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | — | — |
| chat | object | — | — |
| code | integer | — | — |
| contact_removed | boolean | — | — |
| contact_was_new | boolean | — | — |
| date | string | — | — |
| edit_date | string | — | — |
| error | string | — | — |
| error_code | string | — | — |
| exception | object | — | — |
| message_id | integer | — | — |
| ok | boolean | — | — |
| operation | string | — | — |
| params | object | — | — |
| phone_number | string | — | — |
| reply_markup | object | — | — |
| rich | boolean | — | — |
| rich_format | string | — | — |
| sender | object | — | — |
| status | string | — | — |
| text | string | — | — |
| topic_id | integer | — | — |
No examples provided.