telegram-mcp (zai-one/telegram-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 130 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
2 days ago

telegram-mcp

Telegram for AI assistants: conversations, bounded files and voice notes, durable message polling and controlled writes. Read-only by default.

→ zai-one/telegram-mcp· listed on github_repo_search

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

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

zai-one

Source: github_repo_search

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

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
130 tools verified — handlers match their declared behaviour
49 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.
// 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_EXPOSED_TOOLS
configPYTHON_DOTENV_DISABLED
configTELEGRAM_SECRET_FILE
configTELEGRAM_BINDINGS_FILE
configTELEGRAM_MCP_PUBLIC_KEY_FILE
configTELEGRAM_WRITE_ENABLED
configTELEGRAM_ENABLED
configTELEGRAM_MEDIA_POLICY_FILE
configTELEGRAM_STATE_PATH
configTELEGRAM_ACCOUNT_ID
configTELEGRAM_LOCAL_PRINCIPAL
configTELEGRAM_MCP_ISSUER
configTELEGRAM_MCP_AUDIENCE
configTELEGRAM_LOCAL_SCOPES
configTELEGRAM_RATE_LIMIT
configTELEGRAM_WRITE_RATE_LIMIT
configTELEGRAM_HIGH_RISK_RATE_LIMIT
configTELEGRAM_MAX_CONCURRENCY
configMCP_HOST
configMCP_PORT
configMCP_TRANSPORT
configTELEGRAM_API_ID
configTELEGRAM_API_HASH
configTELEGRAM_CONNECTION
configTELEGRAM_SESSION_STRING
configTELEGRAM_SESSION_NAME
configTELEGRAM_LOG_FILE
configTELEGRAM_ALLOW_SERVER_ROOTS_FALLBACK
// quality suggestions

Tool annotations

116/130 tools have annotations

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

All four hints declared on every tool

130/130 tools missing one or more hints — telegram_list_chats (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); telegram_get_inbox (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); telegram_search_messages (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +127 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 test coverage

Only 30/130 tools referenced in tests (23%)

Write tests that reference each tool by name so every tool has at least one test.

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/zai-one/telegram-mcp)](https://m8ven.ai/mcp/zai-one/telegram-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 00bc8b09f20f075cce01e33f84a27d690b05f7bb
code hash: 4f07e52149496e87fddbb6c76fa9aa0f68b07d0e29246861a848a9e96bd720b0
verified: 9/10/2026, 4:30:44 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