Skills/npm/mcp-telegram-bot-server

mcp-telegram-bot-server@1.0.11

VERIFIED· startup only

Publisher claims: "A Model Context Protocol (MCP) server for Telegram Bot API integration" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher anhuaxiang · publishing for 528 daysInstalls 805Last detonated 2d ago
$claude mcp add mcp-telegram-bot-server -- npx -y mcp-telegram-bot-server
WatchReport an issue

Coverage

Startup only; authenticated tool behavior not tested.
Tested
server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
Not tested
the tool list (the server exited before answering) · what the tools do when called with real credentials

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_API_TOKEN
Where it talks to
no vendor host named in the code
What the honeypot saw
no credential files read · no network
What we could not test
the tool list (the server exited before answering) · what the tools do when called with real credentials

Connect it with a scoped credential, under the guard. It asks for TELEGRAM_BOT_API_TOKEN and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --net declared -- npx -y mcp-telegram-bot-server

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; startup only; authenticated tool behavior not tested) on 2026-11-12 and scored it 87/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 · 27 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
6.8sprocessdependency install exit 0
27sclaimedstartup only: exited (0) before answering · (node:1191) [UNDICI-EHPA] Warning: EnvHttpProxyAgent is experimental, expect them to change at any time. (Use `node --trace-warnings ...` to show where the warning was created) No bot token
27sprocessscript backend runs setup only
27sprocessno install scripts to re-run

Static findings

MEDIUM
File permission modification commandpackage.json:14 · File permission modification command — agent changes file ownership/permissions"build": "tsc && shx chmod +x dist/*.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
MEDIUM
npx invocation of non-well-known packagedist/cli.js:27 · npx invocation of non-well-known package — may execute untrusted codenpx telegram-bot-mcp-server [options]Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagedist/cli.js:87 · npx invocation of non-well-known package — may execute untrusted codeTELEGRAM_BOT_API_TOKEN=your_token_here npx telegram-bot-mcp-serverFix: Pin versions and sources; vendor anything fetched at install time.
AST06
HIGH
Access to sensitive file pathsdist/cli.js:42 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Run with token in .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
npx invocation of non-well-known packagedist/cli.js:40 · npx invocation of non-well-known package — may execute untrusted codeTELEGRAM_BOT_API_TOKEN=your_token_here npx telegram-bot-mcp-serverFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagedist/cli.js:43 · npx invocation of non-well-known package — may execute untrusted codenpx telegram-bot-mcp-serverFix: Pin versions and sources; vendor anything fetched at install time.
AST06

Cost to the agent

Instructions loaded
≈59 tok
1 file · 9 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-bot-server@1.0.11 as of 2d ago. This is the package itself, not its dependencies.