Fast MCP Telegram
io.github.leshchenko1979/fast-mcp-telegramleshchenko1979streamable-httpv0.46.2Scanned
Multi-tenant Telegram gateway for AI agents — HTTP+stdio, 8 tools, MTProto User API
8 tools: 4 can delete or cancel things and 4 only read.
- Reads private data · 4
- Reads text others write · 8
- Can send data out · 3
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Fast MCP Telegram can do
The Fast MCP Telegram is published by the GitHub account leshchenko1979. It has 8 tools. It can delete or cancel things (4 tools: send_message, edit_message, send_message_to_phone and invoke_mtproto). 4 tools only read.
4 tools read private data (search_messages_globally, get_messages, find_chats and 1 more); 8 tools bring in text other people can write (search_messages_globally, get_messages, send_message and 5 more); 3 tools can send data out of your system (send_message, edit_message and send_message_to_phone). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 2 findings (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 11, 2026, version 0.46.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Deletes or cancels 4Claude Code: deny
edit_messageReplace the text of an existing message in a Telegram chat.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "edit_message" says "edit": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "edit_message" says "edit" and "message": it writes something other people read.
Description, as the server wrote it 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). schedule_date (ISO 8601) reschedules an already-queued message; it does not turn a delivered message into a scheduled one, and the result then carries status='scheduled'. 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
Annotations the server declares
- title: Edit message
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
invoke_mtprotoLow-level Telegram API (MTProto) invoke for methods not wrapped by other tools.Reads text others write2 findings
Why it is in this group
- The name "invoke_mtproto" says "invoke": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...esult dict or normalized error. PII and credential-shaped fields (phone, access_hash) are..."
- Info
The input schema at properties.include_sensitive.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.include_sensitive.description: "...return the raw result including PII and credential-shaped fields (phone, access_hash). Def..."
Description, as the server wrote it 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. PII and credential-shaped fields (phone, access_hash) are dropped from a successful result by default; pass include_sensitive=true for the raw payload. A bare message id needs a chat binding: requests with no peer field (messages.GetMessages, messages.DeleteMessages) are refused, because a bare id resolves against an arbitrary dialog. Use channels.GetMessages or messages.GetHistory, which carry the binding. messages.GetHistory cannot address a forum topic (no thread_id/top_msg_id in the schema, and channels.GetHistory does not exist) -- use messages.Search with top_msg_id, or the high-level get_messages with reply_to_id. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md
Annotations the server declares
- title: Invoke MTProto
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: true
send_messageSend text and optional file attachments to a Telegram chat.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "send_message" says "send": a word for sending, and what is sent cannot be taken back.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "send_message" says "send": it sends or publishes something to other people.
Description, as the server wrote it 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. schedule_date (ISO 8601, must be in the future) queues the message instead of delivering it now, so the result carries status='scheduled' plus scheduled and schedule_date. save_as_draft=true saves the text as the chat's draft instead of sending it (empty message clears the draft; user sessions only, bots cannot; text-only, so no files, no parse_mode='rich', no schedule_date). 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
Annotations the server declares
- title: Send message
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: true
send_message_to_phoneSend to a phone number: may create a temporary contact, then send text or files.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "send_message_to_phone" says "send": a word for sending, and what is sent cannot be taken back.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "send_message_to_phone" says "send": it sends or publishes something to other people.
Description, as the server wrote it 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. schedule_date (ISO 8601, future) queues the message instead of delivering now; save_as_draft=true saves the text as the draft in that chat instead of sending. 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
Annotations the server declares
- title: Send message to phone
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: true
Only reads 4Show 4 read-only tools
find_chatsFind users/groups/channels by name, username, or phone.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "find_chats" says "find": a word for reading.
What it can reach
- private-dataThe name "find_chats" says "find" and "chat": it reads messages.
- private-dataThe input names a folder (input.folder), and the tool reads: it reads files.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe name "find_chats" says "find" and "chat": it reads messages, which other people can write.
Description, as the server wrote it 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
Annotations the server declares
- title: Find chats
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_chat_infoLoad profile and metadata for one user, bot, group, or channel.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_chat_info" says "get": a word for reading.
What it can reach
- private-dataThe name "get_chat_info" says "get" and "chat": it reads messages.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe name "get_chat_info" says "get" and "chat": it reads messages, which other people can write.
Description, as the server wrote it Load profile and metadata for one user, bot, group, or channel. Success: info dict; forum chats may include topics up to topics_limit; user targets may include common_chats up to common_chats_limit. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md
Annotations the server declares
- title: Get chat info
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_messagesRead or search messages in one chat: browse latest, search text, fetch by ids, or load replies to a message (comments, forum topics, threads).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_messages" says "get": a word for reading.
What it can reach
- private-dataThe name "get_messages" says "get" and "message": it reads messages.
- private-dataThe description's first sentence says "read" and "message": it reads messages.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe name "get_messages" says "get" and "message": it reads messages, which other people can write.
- untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
Description, as the server wrote it 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. Results are ordered by ascending date-time (oldest first) in every mode, including message_ids and nested context lists; limit selects the newest N. 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
Annotations the server declares
- title: Get messages in chat
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
search_messages_globallySearch all Telegram chats at once (not scoped to one chat).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "search_messages_globally" says "search": a word for reading.
What it can reach
- private-dataThe name "search_messages_globally" says "search" and "message": it reads messages.
- private-dataThe description's first sentence says "search" and "chat": it reads messages.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe name "search_messages_globally" says "search" and "message": it reads messages, which other people can write.
- untrusted-inputThe description's first sentence says "search" and "chat": it reads messages, which other people can write.
Description, as the server wrote it Search all Telegram chats at once (not scoped to one chat). Comma-separated query terms; optional filters by date, chat kind, and public username. Results are ordered by ascending date-time (oldest first); limit selects the newest N. 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
Annotations the server declares
- title: Search messages globally
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
96 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 3 outbound tools breaks every one.
- Reads private data4
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write8
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out3
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__fast-telegram__edit_message",
"mcp__fast-telegram__send_message",
"mcp__fast-telegram__send_message_to_phone"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:07 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 destructive). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://tg-mcp.l1979.ru/v1/mcp: tools/list returned 8 tools to an anonymous client, including send_message (destructive), edit_message (destructive), send_message_to_phone (destructive), invoke_mtproto (destructive)
Findings
Matches of fixed checks, with the text they matched.
- Infoinvoke_mtproto
The description mentions "credential".
What this check looks forMatched text
description: "...esult dict or normalized error. PII and credential-shaped fields (phone, access_hash) are..."
- Infoinvoke_mtproto
The input schema at properties.include_sensitive.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.include_sensitive.description: "...return the raw result including PII and credential-shaped fields (phone, access_hash). Def..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools8 changed.~8 changedView diff
- Changed:edit_messageDeletes or cancelsannotations
- Changed:find_chatsOnly readsannotations
- Changed:get_chat_infoOnly readsannotations
- Changed:get_messagesOnly readsannotations
- Changed:invoke_mtprotoDeletes or cancelsannotations
- Changed:search_messages_globallyOnly readsannotations
- Changed:send_messageDeletes or cancelsannotations
- Changed:send_message_to_phoneDeletes or cancelsannotations
Install
Pinned to version 0.46.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http fast-telegram https://tg-mcp.l1979.ru/v1/mcpclaude mcp add --transport http fast-telegram https://tg-mcp.l1979.ru/v1/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__fast-telegram__search_messages_globally",
"mcp__fast-telegram__get_messages",
"mcp__fast-telegram__find_chats",
"mcp__fast-telegram__get_chat_info"
],
"ask": [],
"deny": [
"mcp__fast-telegram__send_message",
"mcp__fast-telegram__edit_message",
"mcp__fast-telegram__send_message_to_phone",
"mcp__fast-telegram__invoke_mtproto"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as fast-telegram. Review it before you use it.
Capability tags behind 8 rules
- mcp__fast-telegram__search_messages_globally private-data, untrusted-input
- mcp__fast-telegram__get_messages private-data, untrusted-input
- mcp__fast-telegram__send_message untrusted-input, outbound
- mcp__fast-telegram__edit_message untrusted-input, outbound
- mcp__fast-telegram__find_chats private-data, untrusted-input
- mcp__fast-telegram__get_chat_info private-data, untrusted-input
- mcp__fast-telegram__send_message_to_phone untrusted-input, outbound
- mcp__fast-telegram__invoke_mtproto untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.leshchenko1979/fast-mcp-telegram/verify?hash=3230f42d5dce902a99fd24cad8324fd03385dbd1a8c6b2ca2bffb04ff0e0179c" | jq -e '.changed == false'Pinned hash 3230f42d5dce, from Nov 11, 2026, 05:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.leshchenko1979/fast-mcp-telegram/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.leshchenko1979/fast-mcp-telegram)Source: MCP Registry · repository. Synced Nov 11, 2026, 05:17 UTC.
Fast MCP Telegram: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Fast MCP Telegram safe?
- No scan can promise that. What its definitions show: 8 tools, 4 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Fast MCP Telegram delete data?
- Yes. 4 tools can delete, cancel or revoke something: send_message, edit_message, send_message_to_phone and invoke_mtproto.
Can the Fast MCP Telegram do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Fast MCP Telegram have?
- 8 tools: 4 destructive, 4 read. send_message, edit_message, send_message_to_phone, invoke_mtproto, search_messages_globally, get_messages, find_chats and get_chat_info.
Does the Fast MCP Telegram need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Fast MCP Telegram send data to outside services?
- 3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_message, edit_message and send_message_to_phone.
Has the Fast MCP Telegram changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.