updated 2026-08-12 05:02 UTC

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 Grade D Listed Apache-2.0
36.0/100
Rank #683 of 1283
Compare Better Telegram MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-12 · 0d ago
Recent change
Rank +1

Is Better Telegram MCP safe? Better Telegram MCP scores 36.0/100 (Grade D), ranked #683 of 1283 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 77% of recent commits are signed; last pushed 2026-08-12. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#297 Email MCP — 36.3 (D) → #298 Appwrite MCP — 36.1 (D) → #300 Lunch Money — 35.8 (D) → #301 Filesystem MCP — 35.8 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 34 spots (#650 → #684)
2026-08-08
Newly Listed
First tracked at rank #643
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent Get email alerts for Better Telegram MCP View MCP Servers Report missing data
52.8
Activity sub-score · out of 100
#299
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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
10
Forks
3
Last Push
2026-08-12
today
Commits (4 wk)
31
Downloads (7d)
246
pypi
HN mentions (30d)
—
Open Issues
5
Rank Change
▲2
was #685

Analysis

HVTrust Dimensions vs MCP Servers

36.0 / 100 · 67.0% confidence

Better Telegram MCP MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.9 / 25
1.1 below avg 5.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.5 below avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
18.0 / 20
5.6 above avg 12.4
AdoptionLog-scaled stars · package downloads
5.7 / 20
in line with avg 5.8

Activity Inputs

52.8 / 100
StarsRepository reach
6.2 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
18.8 / 25
CommunityFork signal
2.8 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
77%
of last 100 commits verified

Is Better Telegram MCP safe?

Public trust evidence for Better Telegram MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
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?
No OpenSSF Scorecard data is currently published for Better Telegram MCP. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Better Telegram MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
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?
77% 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
medium 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.
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

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
Listed 1Rank 1
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
HVTrust 36.0 Grade D
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON