Telegram Bot (npm) MCP Server

telegram-bot-mcp-server npm v1.0.0

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

A Model Context Protocol (MCP) server for Telegram Bot API integration

View on npm ↗ Raw report (JSON) ↗

Trust grade

95/100

Last scanned 2026-09-07 get badge →

Trust

A · 95/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 = 95/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 − 5 = 95. 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
−2	publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 16

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

send-messagenetwork egress
get-chatno sensitive capability
get-chat-memberno sensitive capability
get-chat-member-countno sensitive capability
get-meno sensitive capability
get-my-commandsno sensitive capability
get-my-descriptionno sensitive capability
get-my-nameno sensitive capability
get-my-short-descriptionno sensitive capability
kick-chat-memberno sensitive capability

Show 6 more tools ↓

send-photono sensitive capability
set-my-commandsno sensitive capability
set-my-descriptionno sensitive capability
set-my-nameno sensitive capability
set-my-short-descriptionno sensitive capability
un-ban-chat-memberno sensitive capability

What this scan could not see

Tools were statically extracted from the published source (16 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
`v1.0.0` latest	A 95/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/telegram-bot-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/telegram-bot-mcp-server)

HTML

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

Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/telegram-bot-mcp-server/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 telegram-bot-mcp-server --online

Use the free API → How scoring works

Other implementations of Telegram Bot 7

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

Telegram Bot (node2flow) npm

@node2flow/telegram-bot-mcp

MCP server for Telegram Bot API — send messages, manage chats, webhooks, files, and more through 27 tools

Marketing & Social Score 99/100 0 findings 135/wk Cap. Minimal

Telegram Bot (bossforce.ai) npm

@bossforce.ai/mcp-telegram-bot

MCP server for the Telegram **Bot API** (a bot identity created via @BotFather). For acting as a personal Telegram account (MTProto), see a future `telegram-user` server — that is a different API with different auth and risks.

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

Telegram Bot (turtus) npm

@turtus/telegram-bot-mcp

MCP server for Telegram Bot API

Marketing & Social Score 98/100 0 findings 16/wk Cap. Minimal

Telegram Bot (PyPI) PyPI

telegram-bot-mcp

Telegram Bot MCP Server - publish, edit, and search messages in Telegram channels

Web, Search & Scraping Score 98/100 0 findings Cap. Minimal

Telegram Bot (mcp-telegram-bot) npm

mcp-telegram-bot

MCP server for Telegram bot operations including posting, reactions, polls and blog management