Skills/npm/telegram-bot-mcp-server

telegram-bot-mcp-server@2.0.0

VERIFIED

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 null-topology · publishing for 33 daysInstalls 785Last detonated 4d ago
$claude mcp add telegram-bot-mcp-server -- npx -y @null-topology/telegram-bot-mcp-server
WatchReport an issue

Coverage

Started with a decoy TELEGRAM_BOT_API_TOKEN; tool list observed. Tool calls with a real credential not tested.
Tested
server startup with a tagged decoy in TELEGRAM_BOT_API_TOKEN · MCP initialize and tools/list · every tool description, for hidden instructions · where the decoy credential went · every file read, file written and host contacted by what ran
Not tested
what the tools do when called with a real credential
Needs
TELEGRAM_BOT_API_TOKEN — give it to the server where it runs, through vet-skills run --secrets, so the value never enters the server's environment. Never paste a credential into a chat, a ticket or a report.

Before you give it your token

It will ask for
TELEGRAM_BOT_API_TOKENConfiguration, not credentials: TELEGRAM_DOWNLOAD_DIR, TELEGRAM_UPLOAD_ROOTS
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
what the tools do when called with a real credential

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.

$vet-skills run --net declared -- npx -y @null-topology/telegram-bot-mcp-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) on 2026-11-10 and scored it 86/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 52 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
11sprocessdependency install exit 0
32sprocessrelaunched with a decoy TELEGRAM_BOT_API_TOKEN (tagged; nothing real)
52sclaimed50 tools with a decoy TELEGRAM_BOT_API_TOKEN: get-me, set-my-short-description, get-my-short-description, set-my-commands, get-my-commands, set-my-name, get-my-name, set-my-description, get-my-description, send-message, send-chat-action, forward-message, copy-message, edit-message-text, edit-message-caption, set-message-reaction, delete-message, pin-chat-message, unpin-chat-message, unpin-all-chat-messages, send-photo, send-document, send-video, send-audio, send-voice
52sprocessscript backend runs setup only
52sprocessno install scripts to re-run

Static findings

MEDIUM
npx invocation of non-well-known package.build/cli.js:21 · npx invocation of non-well-known package — may execute untrusted codenpx @null-topology/telegram-bot-mcp-server [options]Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagepackage.json:32 · npx invocation of non-well-known package — may execute untrusted code"build": "npx tsc",Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
HIGH
Access to sensitive file paths.build/cli.js:53 · 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 package.build/cli.js:105 · npx invocation of non-well-known package — may execute untrusted codeTELEGRAM_BOT_API_TOKEN=your_token_here npx @null-topology/telegram-bot-mcp-serverFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known package.build/cli.js:54 · npx invocation of non-well-known package — may execute untrusted codenpx @null-topology/telegram-bot-mcp-serverFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known package.build/cli.js:51 · npx invocation of non-well-known package — may execute untrusted codeTELEGRAM_BOT_API_TOKEN=your_token_here npx @null-topology/telegram-bot-mcp-serverFix: Pin versions and sources; vendor anything fetched at install time.
AST06

Cost to the agent

Instructions loaded
≈63 tok
1 file · 22 in bundle
Tool list per prompt
≈11,142 tok
50 tools · 223 per tool
Handshake
940 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 189

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 @null-topology/telegram-bot-mcp-server@2.0.0 as of 4d ago. This is the package itself, not its dependencies.