q0t-telegram-mcp@0.11.1
VERIFIED· not startedPublisher claims: "Telegram MCP server that actually sends messages" 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
- 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.
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-15 and scored it 91/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
- Update `CLAUDE.md` if the project structure changedFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.- Update `CLAUDE.md` if anything changedFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.… applied in `register_tools`, not in each tool. `functools.wraps` is enough for MCPServer to derive the same schema and find `ctx`. HTTP-integration fakes are plain `MagicMock`s, so give them every method the wrapper…Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.- Update `CLAUDE.md` if the project structure or tech stack changed from what's written thereFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.- Update `CLAUDE.md` if anything changedFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.- [ ] **Step 5: Update the project structure block in `CLAUDE.md`**Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.- Modify: `CLAUDE.md` (project structure block — `folders.py` is new)Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.git add README.md CHANGELOG.md CLAUDE.md pyproject.tomlFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.# {"error": ...} for the model to read, not kill the MCP session.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."""A fresh MCPServer over HTTP with Telethon mocked.Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.server = MCPServer("q0t-telegram-mcp-test-sse", lifespan=lifespan)Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.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 q0t-telegram-mcp@0.11.1 as of 35 min ago. This is the package itself, not its dependencies.