Telegram (mcp-telegram)
Telegram MCP server: connect your personal Telegram account to Claude, ChatGPT, Cursor and any MCP client. 182 tools over MTProto. Self-host with npx or Docker, or use the hosted version.
Is Telegram (mcp-telegram) safe? Strong public trust posture, backed by multiple independent signals.
Compare Telegram (mcp-telegram)
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Telegram (mcp-telegram) scores 77.3/100 (Grade B), ranked #236 of 1374 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 4.3/10; 46% of recent commits are signed; no published advisory affects its latest release (@overpod/mcp-telegram); last pushed 2026-11-02. Every point is earned from checkable signals — never paid placement. How scoring works →
How Telegram (mcp-telegram) could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard from 4.3 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Contributors 0 +9.5 → 86.8 A · #24 of 778
- Sign every commit46% signed today +2.7 → 80.0 A · #99 of 778
Chain of custody
Scanners check what the code says. This traces who ships Telegram (mcp-telegram) and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/mcp-telegram/mcp-telegram, MIT, last pushed 2026-11-02. 46% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 4.3/10 (scanned Oct 25, 2026, refresh pending). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies7
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 3CI-Tests 6CII-Best-Practices 0Code-Review 0Contributors 0Dangerous-Workflow 10Dependency-Update-Tool 0Fuzzing 0License 10Maintained 10Packaging 10Pinned-Dependencies 7SAST 0Security-Policy 10Signed-Releases 0Token-Permissions 0Vulnerabilities 0 -
Published packages Linked and attested
- npm @overpod/mcp-telegram Source link points back to this repo Build provenance attested
-
What you install today No known advisories
Latest release checked: @overpod/mcp-telegram 1.45.1. No published advisory affects it (OSV, checked 2026-11-09).
Changes to this chain
- 2026-09-23 Package provenance attestation detected
- 2026-09-03 Package provenance attestation detected
- 2026-08-30 OSSF Scorecard: 3.2/10
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Telegram (mcp-telegram)’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Telegram (mcp-telegram) compares in MCP Servers
- #132 MCP Rubber Duck 77.7 +0.4
- #133 Dynatrace Managed MCP 77.4 +0.1
- #134 Telegram (mcp-telegram) 77.3 this agent
- #135 Outline MCP Server 77.2 −0.1
- #136 Talkthrough MCP 77.0 −0.3
Bars show each HVTrust score; the tick marks Telegram (mcp-telegram)’s 77.3.
Where the 77.3 comes from
HVTrust dimensions vs the MCP Servers average
77.3 / 100 · 100.0% confidenceTelegram (mcp-telegram) MCP Servers average (778 agents)
Quick Trust Read
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
Activity & Reach
Analysis
Activity Inputs
58.9 / 100Common questions about Telegram (mcp-telegram)
Does Telegram (mcp-telegram) publish package provenance?
Does Telegram (mcp-telegram) have an OpenSSF Scorecard?
Is Telegram (mcp-telegram) actively maintained?
What license does Telegram (mcp-telegram) use?
Are Telegram (mcp-telegram)'s commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
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.
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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/telegram-mcp-telegram)
<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
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.4 · Raw JSON