MCP Telegram Cloud (kaka-sangi/mcp-telegram-cloud-deploy) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 181 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
1 month ago

MCP Telegram Cloud

Open source MCP server that connects a Telegram account to AI assistants over OAuth + QR login, enabling read-only and safe state-change operations.

→ kaka-sangi/mcp-telegram-cloud-deploy· listed on glama

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

kaka-sangi

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

Glamanot scored here

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
✅
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 5 credentials: ADMIN_TOKEN, SESSION_ENCRYPTION_KEY, TELEGRAM_2FA_PASSWORD, TELEGRAM_PROXY_PASSWORD, TELEGRAM_PROXY_SECRET
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.
🔐 secretADMIN_TOKENand ISSUER (your public HTTPS URL). is optional but
configBRAND_NAME
configCONTACT_EMAIL
configCONTACT_TELEGRAM
configDATABASE_PATH
configDESTRUCTIVE_AUDIT_RETENTION_DAYS
configDESTRUCTIVE_DAILY_LIMIT
configFREE_TIER_LIMIT
configISSUERand (your public HTTPS URL). ADMIN_TOKEN is optional but
configISSUES_LABEL
configISSUES_URL
configLOG_HASH_SALT
configLOG_SERVICE_NAME
configLOG_USER_IDS
configMAX_JSON_BODY_BYTES
configMAX_OAUTH_CLIENTS
configMCP_DRAIN_HEALTH_DELAY_MS
configMCP_DRAIN_POLL_MS
configMCP_DRAIN_TIMEOUT_MS
configMCP_IDLE_REAP_INTERVAL_MS
configMCP_IDLE_REAP_MS
configMCP_RATE_LIMIT
configMCP_RATE_WINDOW_MS
configMCP_TELEGRAM_DAEMON
configMCP_TELEGRAM_ENABLE_GROUP_CALLS
configMCP_TELEGRAM_ENABLE_QUICK_REPLIES
configMCP_TELEGRAM_ENABLE_STARS
configMCP_TELEGRAM_TELEMETRY
configOAUTH_RATE_LIMIT
configOAUTH_RATE_WINDOW_MS
configOPENAI_APPS_CHALLENGE
configREGISTER_RATE_LIMIT
configREGISTER_RATE_WINDOW_MS
🔐 secretSESSION_ENCRYPTION_KEY
configSIGNOZ_AUTH
configSIGNOZ_ENDPOINTCloud, etc.), or stderr if is empty
configSOURCE_REPO_URL
🔐 secretTELEGRAM_2FA_PASSWORD
configTELEGRAM_API_HASHfill in TELEGRAM_API_ID + (from https://my.telegram.org/apps)
configTELEGRAM_API_IDfill in + TELEGRAM_API_HASH (from https://my.telegram.org/apps)
configTELEGRAM_LOG_LEVEL
configTELEGRAM_PROXY_IP
🔐 secretTELEGRAM_PROXY_PASSWORD
configTELEGRAM_PROXY_PORT
🔐 secretTELEGRAM_PROXY_SECRET
configTELEGRAM_PROXY_SOCKS_TYPE
configTELEGRAM_PROXY_USERNAME
configTELEGRAM_SESSION_PATH
configTELEGRAM_USE_WSS
configTRAEFIK_YAML_PATH
configUNUSED_CLIENT_TTL_DAYS
configUPLOAD_FILE_MAX_BYTES
configUPLOAD_QUOTA_BYTES
configUPLOAD_TTL_SECONDS
configUSAGE_LOG_RETENTION_DAYS
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

181/181 tools missing one or more hints — telegram-mute-chat (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); telegram-get-chat-folders (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); telegram-set-auto-delete (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +178 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

163/181 tool handlers declare input schemas (90%)

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

Tool handlers catch errors

180/181 tool handlers wrap calls in try/catch (99%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

Only 3/181 tools referenced in tests (2%)

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

Shell command execution

13 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

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 6 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/kaka-sangi/mcp-telegram-cloud-deploy)](https://m8ven.ai/mcp/kaka-sangi/mcp-telegram-cloud-deploy)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 9c0e4ea0de096a0a49c6b9d5a81f008f7b664ca3
code hash: a3ffe175d493859c7502a73de06b04d46a51d9c0d8aa04b4e720c2b365cfea97
verified: 7/21/2026, 9:32:39 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