uniquedivine-telegram-mcp@2.0.5
CAUTION· not startedPublisher claims: "Telegram MCP server maintained in Jiyuu. Reads and manages chats, messages, contacts, folders, and media through your Telegram user account." 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: 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, t.me — not the publisher's domain; check what for before connecting.
- 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 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.
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 69/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; Prompting user to enter sensitive credentials. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
print("The generated session string can be added to your .env file.")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.module = importlib.util.module_from_spec(spec)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.print("Add this to your .env file as:")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.assert prompted == ["Two-factor authentication enabled. Please enter your password: "]Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."\nTwo-factor authentication enabled. Please enter your password: "Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."TELEGRAM_SESSION_STRING or TELEGRAM_SESSION_STRING_<LABEL> in .env. "Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.print("Error: TELEGRAM_API_ID and TELEGRAM_API_HASH must be set in .env file")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.raw_path="../etc/passwd",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."Set TELEGRAM_SESSION_STRING or TELEGRAM_SESSION_STRING_<LABEL> in .env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."\nWould you like to automatically update your .env file with this session string? (y/N): "Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.return subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.run = lambda *args: subprocess.run( # noqa: E731Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.spec.loader.exec_module(module)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.assert prompted == ["\nTwo-factor authentication enabled. Please enter your password: "]Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.raw_path="missing.txt", ctx=None, tool_name="send_file"Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.print("Create an .env file with your credentials from https://my.telegram.org/apps")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.pw = getpass.getpass("Two-factor authentication enabled. Please enter your password: ")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.commit = subprocess.run(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 uniquedivine-telegram-mcp@2.0.5 as of 25 h ago. This is the package itself, not its dependencies.
What would make this Verified
11 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim unique-divine: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- 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.
- Prompting user to enter sensitive credentials≈ +2 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.
- Dynamic module loading≈ +1 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.