telegram-mcp-bot@1.0.0
VERIFIED· not startedPublisher claims: "Unified Telegram bot with MCP (Model Context Protocol) for information collection and RAG assistant" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
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
CHROMA_OPENAI_API_KEYGIGACHAT_AUTHLLM_PROXY_API_KEYTELEGRAM_TOKENWEBHOOK_HOSTWEBHOOK_PATHWEBHOOK_PORTConfiguration, not credentials: GIGACHAT_SCOPE, GROUP_CHAT_ID, LLM_PROXY_API_BASE_URL- Where it talks to
- no vendor host named in the code
- What we saw when it ran
- 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. It asks for CHROMA_OPENAI_API_KEY, GIGACHAT_AUTH, LLM_PROXY_API_KEY, TELEGRAM_TOKEN, WEBHOOK_HOST, WEBHOOK_PATH, WEBHOOK_PORT 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.
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-19 and scored it 81/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 deviationsStatic findings
raise ValueError("TELEGRAM_TOKEN не установлен в .env")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.RUN curl -fsSL https://deb.nodesource.com/setup_20.x | bash - \Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.print("\n✅ Configuration saved to .env")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.with open(".env", "w") as f:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.default=".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.# Write .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.&& rm -rf /var/lib/apt/lists/*Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.raise ValueError("TELEGRAM_TOKEN не установлен в .env")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.raise ValueError("TELEGRAM_TOKEN не установлен в .env")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.default=".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.RUN npx playwright install chromiumFix: Pin versions and sources; vendor anything fetched at install time.RUN npx playwright install-deps chromiumFix: Pin versions and sources; vendor anything fetched at install time.RUN curl -fsSL https://deb.nodesource.com/setup_20.x | bash - \Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Cost to the agent
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 telegram-mcp-bot@1.0.0 as of 12 h ago. This is the package itself, not its dependencies.