Is Telegram Connector safe and trustworthy?

tashan scores Telegram Connector on public evidence — tashan score 65.0/100, it is currently active, note: a single primary maintainer (bus-factor risk), no known advisories against the current release. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Telegram Connector?

In Claude Code: run `claude mcp add zapier-telegram-connector -- npx -y @zapier/telegram-connector`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

‹ The Index

Telegram Connector

npm

Agent-callable Telegram bot tools — send messages, media, locations, contacts, and polls; edit, delete, forward, copy, and pin messages; resolve chats, members, and files. Use when the user mentions Telegram or wants a bot to post, manage, or look up Tele

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Work: Messaging and email

Who it is for: Operations

Install (Claude Code):

claude mcp add zapier-telegram-connector -- npx -y @zapier/telegram-connector

tashan score: 65.0
Adoption: 490/wk
Upkeep: 72.0
Freshness: 98.0
Evidence coverage: 100% of the inputs this score can use
Health: active
License: Elastic-2.0

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 0.2.18 — this package, not its dependency tree

No access inferred from declared dependenciesnothing it depends on reaches files, shell or network. This reads declarations only — built-in APIs are invisible to it, so absence of a declaration is not absence of access

No build provenanceno attestation — the published artifact cannot be traced to its source

What changed recently

2026-08-16 @zapier/telegram-connector published 0.2.18, was 0.2.15 A new release is available.

You are reading this because you came looking. tashan Pro gives tashan doctor the history behind it, so a run over your own config says which of YOURS moved.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

We recorded 1 change to Telegram Connector in the last 45 days. Pro tells you on the day — for the servers in your own config, not the ones you thought to look up.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-zapier-telegram-connector.svg)](https://tashan.sh/capability/pkg-zapier-telegram-connector.html)

npm ↗ · source ↗ · pkg:@zapier/telegram-connector

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-08-20 · scorer s5 · how · something wrong here?