ModelsAtlas
Explore
Atlas / MCP servers / qpd-v / Telegram Communicator

Telegram CommunicatorSAFE

mcp/qpd-v/telegram-communicator
MCP server by qpd-v · Audited 2026-10-08
⚑ Report / re-scanSource ↗

An MCP server that enables communication with users through Telegram. This server provides a tool to ask questions to users and receive their responses via a Telegram bot.

Verdict
SAFE
Grade
B
Trust score
89 /100
Exposed tools
4 1r · 3w · 0d
Transport
—
License
—
Stars
47
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

An MCP server that enables communication with users through Telegram. This server provides tools to interact with users via a Telegram bot, including asking questions, sending notifications, sharing files, and creating project archives.

Installation

Via npm (global)

npm install -g mcp-communicator-telegram

Via npx (on-demand)

npx mcptelegram

To get your Telegram chat ID:

npx mcptelegram-chatid

Features

  • Ask questions to users through Telegram
  • Send notifications to users (no response required)
  • Send files to users via Telegram
  • Create and send project zip files (respecting .gitignore)
  • Receive responses asynchronously (waits indefinitely for response)
  • Support for reply-based message tracking
  • Secure chat ID validation
  • Error handling and logging

Prerequisites

  • Node.js (v14 or higher)
  • A Telegram bot token (obtained from @BotFather)
  • Your Telegram chat ID (can be obtained using the included utility)

Installation

  1. Clone the repository:
git clone https://github.com/qpd-v/mcp-communicator-telegram.git
cd mcp-communicator-telegram
  1. Install dependencies:
npm install
  1. Create a Telegram bot:
  2. Open Telegram and search for @BotFather
  3. Send /newbot and follow the instructions
  4. Save the bot token you receive
  1. Get your chat ID:
  2. Copy .env.example to .env
  3. Add your bot token to the .env file:
TELEGRAM_TOKEN=your_bot_token_here
  • Run the chat ID utility:
npm run build
node build/get-chat-id.js
  • Send any message to your bot
  • Copy the chat ID that appears in the console
  • Add the chat ID to your .env file:
TELEGRAM_TOKEN=your_bot_token_here
CHAT_ID=your_chat_id_here

Configuration

Add the server to your MCP settings file (usually located at `%APPDATA%\Code\Use

Read from source at commit 7fc93433a9c3OBSERVED · 2026-10-08
02

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.

claude-code
claude mcp add mcp-communicator-telegram --env TELEGRAM_TOKEN=${TELEGRAM_TOKEN} -- npx -y [email protected]
claude-desktop
{
  "mcpServers": {
    "mcp-communicator-telegram": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ],
      "env": {
        "TELEGRAM_TOKEN": "${TELEGRAM_TOKEN}"
      }
    }
  }
}
03

Exposed tools (4)

1 read · 3 write · 0 destructive.

ToolRiskDescription
ask_userreadAsk the user a question via Telegram and wait for their response
notify_userwriteSend a notification message to the user via Telegram (no response required)
send_filewriteSend a file to the user via Telegram
zip_projectwriteZip a project directory and send it to the user
04

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryWARN
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
none-observed
Shell
none-observed
Dependencies
not all pinned
Secrets in source
none-found

Findings (3)

MEDIUMInventory / provenance · inv.binary · CWE-1104
project.zip
project.zip
Why it matters. a compiled or binary member cannot be reviewed from source
Fix. ship source, or explain the binary in the README
LOWInventory / provenance · inv.no_license · CWE-1104
Why it matters. no LICENSE file and no repo licence
Fix. add a licence
LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
package.json
archiver, dotenv, ignore, node-telegram-bot-api, @types/archiver, @types/node, @types/node-telegram-bot-api, rimraf
Why it matters. 9 dependency range(s) float
Fix. pin exact versions or ship a lockfile

Gates applied: no_behavioural_pass, no_license.

Audited 2026-10-08 · audit v0.4.1 · source sha 7fc93433a9c3full audit observations/trust-audit/mcp-server/qpd-v__telegram-communicator.json · Report an issue / request a re-scan
05

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-087fc93433a9c3SAFEB89first audit
06

Questions

What is the Telegram Communicator MCP server?

An MCP server that enables communication with users through Telegram. This server provides a tool to ask questions to users and receive their responses via a Telegram bot.

What tools does Telegram Communicator expose?

4 in total: 1 read-only, 3 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.

Is Telegram Communicator safe to connect to an agent?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.

What credentials does Telegram Communicator need?

It reads TELEGRAM_TOKEN from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.

How current is this page?

The grade is for one exact copy of the source (7fc93433a9c3), read on 2026-10-08. The repository is watched and re-audited when it changes.

Advertisement