Telegram MCP Server (Asadullayev06/telegram-mcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Limited view
71/100
28 days ago

Telegram MCP Server

A Telegram integration for Claude, Cursor, and other MCP-compatible clients. It exposes Telegram account, chat, message, contact, media, folder, and admin operations through the Model Context Protocol using Telethon.

→ Asadullayev06/telegram-mcp· 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

Asadullayev06

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
✅
117 tools verified — handlers match their declared behaviour
50 read-only tools verified — handlers contain no write/delete/exec
✅
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: AUTO_REPLY_LLM_API_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.
configTELEGRAM_API_ID, TELEGRAM_API_HASH, or TELEGRAM_SESSION_STRING to that
configTELEGRAM_API_HASHTELEGRAM_API_ID, , or TELEGRAM_SESSION_STRING to that
configAUTO_REPLY_ENABLED
🔐 secretAUTO_REPLY_LLM_API_KEY
configAUTO_REPLY_LLM_MODEL
configAUTO_REPLY_LLM_MAX_TOKENS
configAUTO_REPLY_LLM_TEMPERATURE
configAUTO_REPLY_HISTORY_LIMIT
configAUTO_REPLY_SYSTEM_PROMPT
configAUTO_REPLY_READ_DELAY_MIN
configAUTO_REPLY_READ_DELAY_MAX
configAUTO_REPLY_TYPING_DELAY
configAUTO_REPLY_BLOCKLIST
configMCP_TRANSPORT
configHOST
configMCP_DISABLE_HOST_CHECK
configTELEGRAM_EXPOSED_TOOLSread-only to expose only tools annotated with
configTELEGRAM_SESSION_STRINGTELEGRAM_API_ID, TELEGRAM_API_HASH, or to that
configTELEGRAM_SESSION_NAMENo Telegram session configured: set TELEGRAM_SESSION_STRING, , or suffixed multi-account variants.
configMCP_DEFAULT_ROOT
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

All four hints declared on every tool

117/117 tools missing one or more hints — list_accounts (missing: destructiveHint, idempotentHint, openWorldHint); get_chats (missing: destructiveHint, idempotentHint); subscribe_public_channel (missing: readOnlyHint), +114 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.

Tool inputs are validated

116/117 tool handlers declare input schemas (99%)

Declare an inputSchema with zod/joi/yup on every tool definition.

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/asadullayev06-telegram-mcp-yz6e5x)](https://m8ven.ai/mcp/asadullayev06-telegram-mcp-yz6e5x)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 7246746e8209f5f9877f6f5020e5f1665301cd7e
code hash: 7f3bb224dc0f074397013edf3282ef6d422d5ac6b707f7e3f6df58a31547a8ae
verified: 8/6/2026, 3:18:55 PM
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