Skip to content

io.github.leshchenko1979/fast-mcp-telegram

by leshchenko1979 · remote · local (pypi) · no sign-in to list tools · v0.46.1 · published by GitHub user leshchenko1979

Multi-tenant Telegram gateway for AI agents — HTTP+stdio, 8 tools, MTProto User API

Deletes · 4
CompareRegistry entry

8 tools: 4 can delete or cancel things and 4 only read.

Scanned Oct 21, 2026

2 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http fast-telegram https://tg-mcp.l1979.ru/v1/mcp

Findings

Matches of fixed checks, with the text they matched.

2 info
  • Infoinvoke_mtproto

    The description mentions "credential".

    Matched text

    description: "...esult dict or normalized error. PII and credential-shaped fields (phone, access_hash) are..."

    What this check looks for
  • Infoinvoke_mtproto

    The input schema at properties.include_sensitive.description mentions "credential".

    Matched text

    inputSchema.properties.include_sensitive.description: "...return the raw result including PII and credential-shaped fields (phone, access_hash). Def..."

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

8 tools

Deletes or cancels 4Claude Code: deny
  • edit_messageReplace the text of an existing message in a Telegram chat.No 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).
    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
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • invoke_mtprotoLow-level Telegram API (MTProto) invoke for methods not wrapped by other tools.2 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).

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...esult dict or normalized error. PII and credential-shaped fields (phone, access_hash) are..."

      What this check looks for
    • Info

      The input schema at properties.include_sensitive.description mentions "credential".

      Matched text

      inputSchema.properties.include_sensitive.description: "...return the raw result including PII and credential-shaped fields (phone, access_hash). Def..."

      What this check looks for
    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
    • destructiveHint: true
    • openWorldHint: true
  • send_messageSend text and optional file attachments to a Telegram chat.No 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).
    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
    • destructiveHint: true
    • openWorldHint: true
  • send_message_to_phoneSend to a phone number: may create a temporary contact, then send text or files.No 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).
    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
    • destructiveHint: true
    • openWorldHint: true
Only reads 4Claude Code: allow
  • find_chatsFind users/groups/channels by name, username, or phone.No findings

    Why it is in this group

    • The name "find_chats" says "find": a word for reading.
    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
    • idempotentHint: true
    • openWorldHint: true
  • get_chat_infoLoad profile and metadata for one user, bot, group, or channel.No findings

    Why it is in this group

    • The name "get_chat_info" says "get": a word for reading.
    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
    • 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).No findings

    Why it is in this group

    • The name "get_messages" says "get": a word for reading.
    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
    • idempotentHint: true
    • openWorldHint: true
  • search_messages_globallySearch all Telegram chats at once (not scoped to one chat).No findings

    Why it is in this group

    • The name "search_messages_globally" says "search": a word for reading.
    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
    • 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.

Install

Pinned to version 0.46.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http fast-telegram https://tg-mcp.l1979.ru/v1/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.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. It assumes the server is installed as fast-telegram. Review it before you use it.