Skills/PyPI/mcp-telegram-bridge

mcp-telegram-bridge@0.2.1

VERIFIED· not started

Publisher claims: "Stdio MCP server: controlled Telegram Bot API bridge for any MCP host." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher antonio-castellon · publishing for 54 daysInstalls 448Last detonated 5d ago
$claude mcp add mcp-telegram-bridge -- uvx mcp-telegram-bridge
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
TELEGRAM_BOT_TOKENConfiguration, not credentials: ALLOW_ALL_CHATS, ALLOWED_CHAT_IDS, INBOUND_CHAT_RATE, INBOUND_GLOBAL_RATE, INBOUND_POLL_RATE, MAX_INBOUND_CHARS, MAX_UPDATE_BYTES, OUTBOUND_CHAT_RATE, OUTBOUND_GLOBAL_RATE, SAFETY_STRICT
Where it talks to
no vendor host named in the codeAlso telegram.org — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names telegram.org as well as its own vendor. The guard injects TELEGRAM_BOT_TOKEN only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- uvx mcp-telegram-bridge

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-10 and scored it 80/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

MEDIUM
Telegram Bot API URLtests/test_abuse.py:17 · Telegram Bot API URL — data will be sent to TelegramAPI = f"https://api.telegram.org/bot{TOKEN}"Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.
AST07
HIGH
Access to sensitive file pathssrc/mcp_telegram_bridge/config.py:259 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filescandidates.append(here.parents[2] / ".env")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/test_safety.py:18 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesassert safety.classify_inbound("show me the .env please") == "secrets"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Hidden zero-width characters detectedtests/test_safety.py:1 · Hidden zero-width characters detected — may conceal content"""Safety classify + scrub tests."""Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.
AST07
HIGH
Access to sensitive file pathssrc/mcp_telegram_bridge/config.py:251 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""Best-effort load of a local .env without adding a hard dependency."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Telegram Bot API URLtests/test_library.py:19 · Telegram Bot API URL — data will be sent to TelegramAPI = f"https://api.telegram.org/bot{TOKEN}"Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.
AST07
HIGH
Access to sensitive file pathssrc/mcp_telegram_bridge/safety.py:36 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files\b(dame|show|give|leak|exfiltrat|cat|print|dump)\b.{0,40}(\.env\b|dotenv|token|password|secret|clave|webhook)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Telegram Bot API URLtests/test_server_tools.py:18 · Telegram Bot API URL — data will be sent to TelegramAPI = f"https://api.telegram.org/bot{TOKEN}"Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.
AST07
MEDIUM
Telegram Bot API URLtests/test_redact.py:36 · Telegram Bot API URL — data will be sent to Telegram"HTTP Request: POST https://api.telegram.org/bot%s/getMe",Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.
AST07
MEDIUM
Telegram Bot API URLtests/test_redact.py:23 · Telegram Bot API URL — data will be sent to Telegramtext = f"https://api.telegram.org/bot{token}/getMe and {encoded}"Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.
AST07
MEDIUM
Python subprocess execution detectedtests/test_library.py:35 · Python subprocess execution detectedresult = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Telegram Bot API URLtests/test_library.py:70 · Telegram Bot API URL — data will be sent to Telegramroute = respx.post(f"https://api.telegram.org/bot{TOKEN}/sendMessage").mock(Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.
AST07
HIGH
Access to sensitive file pathssrc/mcp_telegram_bridge/safety.py:28 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files(?<!\w)\.env(?!\w)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/mcp_telegram_bridge/config.py:201 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"TELEGRAM_BOT_TOKEN is not set. Copy .env.example to .env "Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/mcp_telegram_bridge/config.py:256 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filescandidates.append(Path.cwd() / ".env")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈57 tok
1 file · 31 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for mcp-telegram-bridge@0.2.1 as of 5d ago. This is the package itself, not its dependencies.