Telegram (cloud9-labs) MCP Server

@cloud9-labs/mcp-telegram npm v0.1.0

Published by @cloud9-labs — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for Telegram Bot API

View on npm ↗ Repository ↗ Raw report (JSON) ↗

Trust grade

96/100

Last scanned 2026-09-07 get badge →

Trust

A · 96/100

Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.

Capability

Moderate

Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.

Coverage

Source

How much the scan could actually inspect. Shallow coverage is stated, never hidden.

A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

Points	Adoption-risk factor
−3	capability blast radius (moderate) — client exposure if the model is manipulated
−1	publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 12

Each tool and what it can reach — statically extracted from the published source.

telegram_forward_messagenetwork egress
telegram_send_messagenetwork egress
telegram_set_webhooknetwork egress
telegram_delete_messageno sensitive capability
telegram_edit_messageno sensitive capability
telegram_get_chatno sensitive capability
telegram_get_chat_members_countno sensitive capability
telegram_get_meno sensitive capability
telegram_get_updatesno sensitive capability
telegram_pin_messageno sensitive capability

Show 2 more tools ↓

telegram_send_documentno sensitive capability
telegram_send_photono sensitive capability

What this scan could not see

Tools were statically extracted from the published source (12 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

Version	Score	Findings	Engine	Scanned
`v0.1.0` latest	A 96/100	0	1.13.0	2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

Markdown (GitHub README)

[![MCP Trust Score](https://mcptrustchecker.com/registry/cloud9-labs-mcp-telegram/badge.svg)](https://mcptrustchecker.com/registry/cloud9-labs-mcp-telegram)

HTML

<a href="https://mcptrustchecker.com/registry/cloud9-labs-mcp-telegram"><img src="https://mcptrustchecker.com/registry/cloud9-labs-mcp-telegram/badge.svg" alt="MCP Trust Score" height="20"></a>

Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/cloud9-labs-mcp-telegram/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @cloud9-labs/mcp-telegram --online

Use the free API → How scoring works

Other implementations of Telegram 14

Independent packages implementing the same tool, scanned with the same engine. Compare all 15 side by side →

Telegram (tonresistor) npm

@tonresistor/telegram-mcp

Production-ready MCP Server for Telegram Bot API - 162 methods with token-optimized meta mode

API Development Score 99/100 0 findings 261/wk Cap. Minimal

Telegram (beautyfree) npm

mcp-telegram

Telegram MCP server (MTProto). Connect Claude, Codex, Cursor, Claude Code, VS Code, Cline, Windsurf, and other MCP clients to a real Telegram user account: read dialogs, search messages globally, send/edit/forward, react/poll, moderate channels, tag Saved

Communication & Collaboration Score 99/100 0 findings 192/wk Cap. Minimal

Telegram (kfastov) npm

telegram-mcp-server

MCP server for a Telegram client built with the MTProto library and FastMCP framework

Cloud & DevOps Score 99/100 0 findings 53/wk Cap. Minimal

Telegram (hlos-ai) npm

mcp-server-telegram

MCP server for telegram API integration

Communication & Collaboration Score 99/100 0 findings 15/wk Cap. Minimal

Telegram (zhigang1992) npm

@zhigang1992/telegram-mcp

Telegram MCP server for interacting with Telegram via the Model Context Protocol