Skills/Glama/mcp-server-telegram-bot

mcp-server-telegram-bot@0.4.1

CAUTION· not started

Publisher claims: "Enables AI agents to send Telegram messages, documents, and photos through a user's own bot while keeping the bot token in the environment and restricting access to approved chats and directories." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry GlamaPublisher mirmakhamat · publishing for 11 daysInstalls 0Last detonated 4d ago
What would fix thisWatchDispute verdict

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: Caution 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
no credential variables read in the code
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 under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.

$vet-skills run --net declared -- <the server's command>

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 76/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. 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

HIGH
Access to sensitive file pathssrc/telegram_mcp/server.py:199 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""Send an existing file. Files in the session directory send directly; elsewhere the user is asked. Secrets (.ssh, .env, keys) are always refused."""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 pathspyproject.toml:36 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesinclude = ["src", "tests", "README.md", "pyproject.toml", ".env.example"]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 pathspyproject.toml:35 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesexclude = ["CLAUDE.md", ".env*", "uv.lock"]Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
CRITICAL
Prompt injectionCLAUDE.md:6 · Prompt injection — known jailbreak technique referenceAgent uzoq ishni tugatib natijani Telegramga yuboradi. Token agent kontekstiga tushmaydi, server env'dan o'qiydi.Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.
AST01
MEDIUM
MCP server using network transport (SSE/HTTP)SKILL.md:5 · MCP server using network transport (SSE/HTTP) — data sent over networkMCP server mirmakhamat/mcp-server-telegram-bot on Glama, built from https://github.com/mirmakhamat/mcp-server-telegram-bot.Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
HIGH
Access to sensitive file pathsCLAUDE.md:27 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesNamuna `.env.example` ga yoziladi; haqiqiy `.env` git'ga kirmaydi.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
AWS access key pattern detectedtests/test_security.py:341 · AWS access key pattern detected — possible hardcoded or harvested key"AKIAABCDEFGHIJKLMNOP",Fix: Never read or enumerate credential locations; accept a documented environment variable instead.
AST03
HIGH
Access to sensitive file pathssrc/telegram_mcp/security.py:15 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files".env*", ".netrc", ".pgpass", ".git-credentials", "id_rsa*", "id_ed25519*", "id_ecdsa*", "id_dsa*",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_security.py:349 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesHARMLESS = ["password: required", "the token expires soon", "ssh keys live in ~/.ssh", "id 123456789 done", "sk-learn"]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_security.py:75 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files(tmp_path / ".env").write_text("x")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Telegram Bot API URLsrc/telegram_mcp/telegram.py:25 · Telegram Bot API URL — data will be sent to Telegramr = await client.post(f"https://api.telegram.org/bot{token}/{method}", data=data, files=files)Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.
AST07
MEDIUM
Access to sensitive file pathstests/test_security.py:698 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesenv = tmp_path / ".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_security.py:78 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesfor p in (tmp_path / ".env", tmp_path / ".ssh" / "id"):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_security.py:113 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesfor rel in (".claude/x.json", ".config/gcloud/k", ".git/config", "a/id_rsa", "a/b.pem", "a/.env.local", "mine/f", ".aws/credentials"):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 pathsCLAUDE.md:21 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files- `send_document`/`send_photo`: faqat `ALLOWED_DIRS` (env) ichidagi fayllar. Yo'l `realpath` bilan tekshiriladi (symlink/`..` hiylasiga qarshi). `~/.ssh`, `.env` kabilar hech qachon.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
≈422 tok
2 files · 16 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

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.

What would make this Verified

4 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim mirmakhamat: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
  3. Telegram Bot API URL≈ +4 on the totalReplace encoded or assembled strings with plain literals and remove undeclared network calls.
  4. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
  5. MCP server using network transport (SSE/HTTP)≈ +2 on the totalNamespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
  6. AWS access key pattern detected≈ +2 on the totalNever read or enumerate credential locations; accept a documented environment variable instead.
Publish a new version to Glama, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim mirmakhamatPropose a patch to the maintainer