Skills/npm/siavashdelkhosh81-telegram-bot-mcp-server

siavashdelkhosh81-telegram-bot-mcp-server@1.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 iflow-mcp · publishing for 458 daysInstalls 447Last detonated 8 h ago
$claude mcp add siavashdelkhosh81-telegram-bot-mcp-server -- npx -y @iflow-mcp/siavashdelkhosh81-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_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
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 @iflow-mcp/siavashdelkhosh81-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-14 and scored it 87/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 · 48 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
7.4sprocessdependency install exit 0
27sprocessrelaunched with a decoy TELEGRAM_BOT_API_TOKEN (tagged; nothing real)
47sclaimed16 tools with a decoy TELEGRAM_BOT_API_TOKEN: get-me, send-message, send-photo, kick-chat-member, un-ban-chat-member, get-chat, get-chat-member-count, get-chat-member, 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
47stools486f27507c6b06b1
47stools6545676ad4096649
47stoolsc9464d983df8fd25
47stoolsd9c8b5fb3cd0411d
47stoolse24d8f7f138ba56d
47stools7f72d55a1c20bf72
47stools06d972e477420af6
47stools8f4365c6efc0a391
47stoolsf31418a0bba9617c
47stoolsb97421e5e1b445a0
47stools0d88464ebbb983d7
47stoolsee04ba689bd437ca
47stools6b3a493d6ad37e1a
47stoolsd69e62588dfeda3a
47stoolsf65a946f689fdb3a
47stools4301cda23b01e1b2
47sprocessscript backend runs setup only
47sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathssrc/cli.ts:57 · 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
HIGH
Access to sensitive file paths.build/cli.js:44 · 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 packagepackage.json:1 · npx invocation of non-well-known package — may execute untrusted code…ashdelkhosh81-telegram-bot-mcp-server": ".build/cli.js"}, "scripts": {"build": "npx tsc", "start": "node .build/index.js", "prepublishOnly": "npm run build"}, "dependenc…Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagesrc/cli.ts:104 · 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 packagesrc/cli.ts:58 · 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
MEDIUM
npx invocation of non-well-known package.build/cli.js:45 · 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
MEDIUM
npx invocation of non-well-known package.build/cli.js:89 · 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 packagesrc/cli.ts:42 · 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 package.build/cli.js:29 · 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 package.build/cli.js:42 · 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 packagesrc/cli.ts:55 · 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

Cost to the agent

Instructions loaded
≈71 tok
1 file · 17 in bundle
Tool list per prompt
≈1,632 tok
16 tools · 102 per tool
Handshake
679 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 97

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 @iflow-mcp/siavashdelkhosh81-telegram-bot-mcp-server@1.0.0 as of 8 h ago. This is the package itself, not its dependencies.