Is Telegram (mcp-telegram) safe to use?

Telegram (mcp-telegram) has an HVTrust score of 72.9/100 (Grade B), ranked #266 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Telegram (mcp-telegram)?

Telegram (mcp-telegram) scores 72.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 43 GitHub stars and is categorized under MCP Servers.

Telegram (mcp-telegram)

mcp-telegram/mcp-telegram

Telegram MCP Server — connect Telegram to Claude AI & ChatGPT. 181 tools: messages, media, reactions, polls, stories & more. MTProto userbot. Self-host (npx) or hosted at mcp-telegram.com.

MCP Servers TypeScript Listed MIT

Is Telegram (mcp-telegram) safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.3 / 10

Provenance Attested

Signed commits 28%

Last push 5d ago

Compare Telegram (mcp-telegram)

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Telegram (mcp-telegram) scores 72.9/100 (Grade B), ranked #266 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.3/10; 28% of recent commits are signed; last pushed 2026-09-21. Every point is earned from checkable signals — never paid placement. How scoring works →

How Telegram (mcp-telegram) compares in MCP Servers

#157 Lotus Wisdom 73.1 +0.2
#158 MikroMCP 73.0 +0.1
#159 Telegram (mcp-telegram) 72.9 this agent
#160 db-mcp (SQLite MCP Server) 72.7 −0.2
#161 Configcat MCP Server 72.7 −0.2

Bars show each HVTrust score; the tick marks Telegram (mcp-telegram)’s 72.9.

Where the 72.9 comes from

HVTrust dimensions vs the MCP Servers average

72.9 / 100 · 100.0% confidence

Telegram (mcp-telegram) MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

13.0 / 25

2.7 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.3 / 17

0.9 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

16.8 / 20

4.7 above avg 12.1

AdoptionLog-scaled stars · package downloads

7.8 / 20

0.6 above avg 7.2

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.3/10. Tighten the weakest checks to improve public safety evidence.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Telegram (mcp-telegram) View MCP Servers Report missing data

55.2

Activity sub-score · out of 100

#159

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-21

5 days ago

Commits (4 wk)

Downloads (7d)

726

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #265

Analysis

Activity Inputs

55.2 / 100

StarsRepository reach

9.9 / 30

FreshnessLast push recency

24.3 / 25

ActivityRecent commits

15.9 / 25

CommunityFork signal

5.0 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

3.3 / 10

OpenSSF Scorecard · scanned Sep 25, 2026

Signed Commits

28%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 3

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Common questions about Telegram (mcp-telegram)

Telegram (mcp-telegram) has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Telegram (mcp-telegram) publish package provenance?

Yes. Telegram (mcp-telegram)'s package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Telegram (mcp-telegram) have an OpenSSF Scorecard?

Telegram (mcp-telegram) has an OpenSSF Scorecard score of 3.3/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Telegram (mcp-telegram) actively maintained?

Actively maintained. The repository was pushed to within the last 5 day(s).

What license does Telegram (mcp-telegram) use?

Telegram (mcp-telegram) ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Telegram (mcp-telegram)'s commits signed?

28% of the last 100 commits to Telegram (mcp-telegram) are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

Telegram (mcp-telegram) appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Telegram (mcp-telegram)'s runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-03

Provenance Added

Package provenance attestation detected

Maintain Telegram (mcp-telegram)?

For maintainers

HVTrust scores Telegram (mcp-telegram) from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 691 spots (#953 → #262)

2026-09-23

HVTrust Changed

HVTrust up 47.2pts (25.8 → 73.0)

2026-09-22

Newly Listed

First tracked at rank #953

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-19

Rank Moved

Rank dropped 30 spots (#245 → #275)

2026-09-18

Rank Moved

Rank rose 11 spots (#256 → #245)

2026-09-16

Rank Moved

Rank rose 17 spots (#275 → #258)

2026-09-11

Rank Moved

Rank dropped 10 spots (#252 → #262)

2026-09-10

Rank Moved

Rank rose 14 spots (#266 → #252)

2026-09-08

Rank Moved

Rank dropped 10 spots (#252 → #262)

2026-09-07

Rank Moved

Rank dropped 21 spots (#231 → #252)

2026-09-05

Rank Moved

Rank dropped 57 spots (#174 → #231)

2026-09-03

Provenance Added

Package provenance attestation detected

2026-09-03

Grade Changed

Trust grade D → B

2026-09-03

Rank Moved

Rank rose 878 spots (#1049 → #171)

2026-09-03

HVTrust Changed

HVTrust up 36.6pts (36.7 → 73.3)

2026-09-02

Rank Moved

Rank dropped 46 spots (#1003 → #1049)

2026-09-01

Rank Moved

Rank dropped 43 spots (#960 → #1003)

2026-08-31

Rank Moved

Rank dropped 26 spots (#934 → #960)

2026-08-30

Scorecard Added

OSSF Scorecard: 3.2/10

2026-08-30

Rank Moved

Rank rose 216 spots (#1150 → #934)

2026-08-30

HVTrust Changed

HVTrust up 14.9pts (21.6 → 36.5)

2026-08-29

Rank Moved

Rank dropped 31 spots (#1119 → #1150)

2026-08-28

Rank Moved

Rank dropped 25 spots (#1094 → #1119)

2026-08-27

Rank Moved

Rank dropped 12 spots (#1082 → #1094)

2026-08-26

Rank Moved

Rank dropped 73 spots (#1009 → #1082)

2026-08-25

Rank Moved

Rank rose 11 spots (#1020 → #1009)

2026-08-24

Rank Moved

Rank dropped 14 spots (#1006 → #1020)

2026-08-20

Rank Moved

Rank rose 36 spots (#1056 → #1020)

2026-08-20

Activity Score Changed

Activity score up 12pts (42 → 54)

2026-08-17

Rank Moved

Rank rose 10 spots (#1063 → #1053)

2026-08-16

Rank Moved

Rank dropped 37 spots (#1026 → #1063)

2026-08-13

Rank Moved

Rank dropped 10 spots (#1018 → #1028)

2026-08-12

Rank Moved

Rank rose 15 spots (#1033 → #1018)

2026-08-10

Rank Moved

Rank dropped 59 spots (#962 → #1021)

2026-08-08

Newly Listed

First tracked at rank #950

GitHub → npm: @overpod/mcp-telegram

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/telegram-mcp-telegram.svg)](https://hvtracker.net/agents/telegram-mcp-telegram)
            
HTML:
            <a href="https://hvtracker.net/agents/telegram-mcp-telegram"><img src="https://hvtracker.net/badge/telegram-mcp-telegram.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON