Back to MCP Trust Indexm8ven
C
Limited view
73/100
19 days ago

docker-telethon-plus

Exposes a Telegram user account via MCP, enabling AI agents to send, read, and manage messages, chats, and media using full MTProto access through Telethon. It wraps Telethon behind a JSON HTTP API and MCP endpoint, allowing agents to interact with Telegram as the authenticated user.

→ psyb0t/docker-telethon-plus· listed on glama

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

psyb0t

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: TELETHON_AUTH_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configTELETHON_HTTP_LISTEN_ADDRESSno 0.0.0.0:8080 host:port to bind
configTELETHON_LOG_LEVELno INFO DEBUG, INFO, WARNING, ERROR
configTELETHON_SESSION"1Aa...long-string-from-login-helper..."
configTELETHON_REQUEST_TIMEOUTno 60 Per-request timeout in seconds
configTELETHON_DEVICE_MODELno docker-telethon-plus What Telegram thinks your device is
configTELETHON_SYSTEM_VERSIONno 1.0 Ditto for OS
configTELETHON_APP_VERSIONno 1.0 Ditto for app
configTELETHON_PROXY
configTELETHON_DOWNLOAD_DIRno /tmp/telethon-plus Scratch space for send_file uploads
🔐 secretTELETHON_AUTH_KEYno "" When set, all endpoints require Authorization: Bearer <key>. /healthz stays public. Empty = no auth.
configTELETHON_CACHE_PATH/cache/entities.json Mount /cache as a host volume to keep this across rebuilds
configTELETHON_POST_TO_URL## Outbound webhook —
configTELETHON_POST_TO_TIMEOUT
configTELETHON_SESSION_OUTPUT_FILE
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

35/35 tools missing one or more hints — _call (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_me (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_entity (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +32 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 3 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/psyb0t-docker-telethon-plus-1q4fm3)](https://m8ven.ai/mcp/psyb0t-docker-telethon-plus-1q4fm3)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: eebdd59060cfaf73d143ac7b006239bc119e6928
code hash: 4e4731842286a8ff46acdd51fb8f46baaeaaabe5c475589e374e55e5956d7c79
verified: 8/2/2026, 9:15:32 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client