Is Better Telegram MCP safe to use?

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

What is the trust score for Better Telegram MCP?

Better Telegram MCP scores 67.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 11 GitHub stars and is categorized under MCP Servers.

Better Telegram MCP

n24q02m/better-telegram-mcp

Telegram for AI agents -- messages, chats, media, and contacts across both bot and full user-account modes.

MCP Servers Python Needs review Apache-2.0

Is Better Telegram MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 6.1 / 10

Provenance None

Signed commits 80%

Last push 13d ago

Compare Better Telegram MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Better Telegram MCP scores 67.3/100 (Grade B), ranked #392 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.1/10; 80% of recent commits are signed; last pushed 2026-09-13. Every point is earned from checkable signals — never paid placement. How scoring works →

How Better Telegram MCP compares in MCP Servers

#231 ContextStream 67.4 +0.1
#232 Laravel Boost 67.4 +0.1
#233 Better Telegram MCP 67.3 this agent
#234 Fr0ster MCP Abap Adt 67.3 ±0
#235 Pdf MCP 67.2 −0.1

Bars show each HVTrust score; the tick marks Better Telegram MCP’s 67.3.

Where the 67.3 comes from

HVTrust dimensions vs the MCP Servers average

67.3 / 100 · 100.0% confidence

Better Telegram MCP MCP Servers average (775 agents)

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

11.6 / 25

1.3 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

13.7 / 17

1.5 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

18.3 / 20

6.2 above avg 12.1

AdoptionLog-scaled stars · package downloads

8.2 / 20

1.0 above avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-26

Warning Issued

Warning: eligibility issues detected

2026-09-25

Rank Moved

Rank rose 82 spots (#474 → #392)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

Maintainer Checklist

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

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Review Flags

[5.1] repository is archived

Compare with another agent Get email alerts for Better Telegram MCP View MCP Servers Report missing data

56.1

Activity sub-score · out of 100

#233

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-13

13 days ago

Commits (4 wk)

Downloads (7d)

16,572

docker+pypi

HN mentions (30d)

—

Open Issues

Rank Change

was #392

Analysis

Activity Inputs

56.1 / 100

StarsRepository reach

6.5 / 30

FreshnessLast push recency

23.2 / 25

ActivityRecent commits

22.4 / 25

CommunityFork signal

3.9 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.1 / 10

OpenSSF Scorecard · scanned Sep 23, 2026

Signed Commits

80%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 10

SAST 10

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 9

Common questions about Better Telegram MCP

Better Telegram MCP 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 Better Telegram MCP publish package provenance?

No published build provenance is currently detected for Better Telegram MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Better Telegram MCP have an OpenSSF Scorecard?

Better Telegram MCP has an OpenSSF Scorecard score of 6.1/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 Better Telegram MCP actively maintained?

Maintained. Last push was 13 days ago.

What license does Better Telegram MCP use?

Better Telegram MCP ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Better Telegram MCP's commits signed?

80% of the last 100 commits to Better Telegram MCP 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

Better Telegram MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Anthropic

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration 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 Better Telegram MCP'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

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Better Telegram MCP?

For maintainers

HVTrust scores Better Telegram MCP 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-26

Warning Issued

Warning: eligibility issues detected

2026-09-25

Rank Moved

Rank rose 82 spots (#474 → #392)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 269 spots (#739 → #470)

2026-09-23

HVTrust Changed

HVTrust up 35.0pts (30.1 → 65.1)

2026-09-22

Newly Listed

First tracked at rank #739

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-18

Rank Moved

Rank dropped 10 spots (#418 → #428)

2026-09-16

Rank Moved

Rank dropped 10 spots (#407 → #417)

2026-09-15

Rank Moved

Rank dropped 44 spots (#363 → #407)

2026-09-14

Rank Moved

Rank dropped 12 spots (#351 → #363)

2026-09-13

Warning Issued

Warning: eligibility issues detected

2026-09-13

Rank Moved

Rank rose 15 spots (#366 → #351)

2026-09-10

Rank Moved

Rank dropped 12 spots (#351 → #363)

2026-09-07

Rank Moved

Rank dropped 21 spots (#324 → #345)

2026-09-05

Rank Moved

Rank dropped 61 spots (#257 → #318)

2026-09-04

Scorecard Added

OSSF Scorecard: 6.9/10

2026-09-04

Grade Changed

Trust grade D → B

2026-09-04

Rank Moved

Rank rose 842 spots (#1099 → #257)

2026-09-04

HVTrust Changed

HVTrust up 31.1pts (36.9 → 68.0)

2026-09-03

Rank Moved

Rank dropped 49 spots (#1050 → #1099)

2026-09-02

Rank Moved

Rank dropped 46 spots (#1004 → #1050)

2026-09-01

Rank Moved

Rank dropped 41 spots (#963 → #1004)

2026-08-31

Rank Moved

Rank dropped 30 spots (#933 → #963)

2026-08-30

Rank Moved

Rank dropped 45 spots (#888 → #933)

2026-08-29

Rank Moved

Rank dropped 46 spots (#842 → #888)

2026-08-28

Rank Moved

Rank dropped 19 spots (#823 → #842)

2026-08-27

Rank Moved

Rank dropped 22 spots (#801 → #823)

2026-08-26

Rank Moved

Rank dropped 103 spots (#698 → #801)

2026-08-16

Rank Moved

Rank dropped 14 spots (#683 → #697)

2026-08-10

Rank Moved

Rank dropped 34 spots (#650 → #684)

2026-08-08

Newly Listed

First tracked at rank #643

GitHub → PyPI: better-telegram-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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