Better-TG-CLI (Telegram)
NPM · BETTER-TG-CLI
Telegram on your own account: read, search, send and press bot buttons. Writes need your approval.
Available components
Last scanned (19 hours ago)
Scores higher than 91% of npm servers
Category Communication
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to TheVilfer/better-tg-cli). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 317 tokens (~105/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 25% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 14 Oct 26 +39
- Injection markers: unverified → pass ▲ security
- Stability: unverified → 0.57 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 12 Oct 26 −34
- Stability: 0.23 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Security disclosure: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.33.0 → 0.37.0 functional
- Package version: 0.33.0 → 0.36.0 functional
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +27
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- 1 Oct 26 0
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- Package version: 0.30.0 → 0.33.0 functional
- Package version: 0.30.0 → 0.31.1 functional
- 30 Sept 26 −26
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Dependency health: pass → unverified ▼ functional
- Package version: 0.28.0 → 0.30.0 functional
- Package version: 0.28.0 → 0.29.0 functional
- 29 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 28 Sept 26 −3
- Malware scan: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Known CVEs: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → pass ▲ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.25.0 → 0.28.0 functional
- Package version: 0.25.0 → 0.27.0 functional
- Package version: 0.25.0 → 0.25.2 functional
- Package version: 0.25.0 → 0.25.1 functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Analysed npm/better-tg-cli@0.37.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | TheVilfer/better-tg-cli |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/TheVilfer/better-tg-cli/.github/workflows/release.yml@refs/tags/v0.37.0 |
| Rekor log index | 3226571628 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a86d0dc51f00f4f07ac82172b750504b40b1329d67908f8a3201e2be2d34b5c050d47ad320ffb562b63560bbd3d98529e4694d1b23e50883a20d042a5 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
telegram_help Telegram CLI reference ~42
List telegram CLI commands and flags. Pass grep to filter (e.g. "thread", "search"). Call this before guessing flags.
| Name | Type | Req | Description |
|---|---|---|---|
| grep | string | – | – |
No output schema declared.
No examples provided.
telegram_read Read Telegram ~103
Run a read-only telegram CLI command on the user's account, e.g. ["inbox","-n","10"], ["read","@user","-n","20"], ["search","invoice","--chat","Work"]. args[0] is the command; chats are an ID, @username, "me" or a title. Output is compact text (add "--json" for JSON). watch needs -t or -n.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | yes | – |
No output schema declared.
No examples provided.
telegram_write Write to Telegram ~102
Run a telegram CLI command that sends, edits, deletes or changes something (or saves files: download, sync), e.g. ["send","@user","-"] with stdin as the text. Needs write access, which only the user can enable (`telegram write-access on`). Writes need an ID, @username or exact chat title.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | yes | – |
| stdin | string | – | Text for a "-" argument (message body), avoids quoting issues |
No output schema declared.
No examples provided.
How do I install the Better-TG-CLI (Telegram) MCP server?
Better-TG-CLI (Telegram) runs locally as an npm package, launched with npx -y better-tg-cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · better-tg-cli
claude mcp add thevilfer-better-tg-cli -- npx -y better-tg-cli
What is the Better-TG-CLI (Telegram) MCP server?
Better-TG-CLI (Telegram) is an MCP server listed in the public MCP registry as io.github.TheVilfer/better-tg-cli. Telegram on your own account: read, search, send and press bot buttons. Writes need your approval. This page covers its npm package (better-tg-cli).
Is the Better-TG-CLI (Telegram) MCP server safe to use?
Better-TG-CLI (Telegram) scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Better-TG-CLI (Telegram) MCP server expose?
Better-TG-CLI (Telegram) exposes 3 tools: telegram_help, telegram_read, telegram_write. Their descriptions and schemas cost roughly 247 tokens of context every time the server is loaded.
Is the Better-TG-CLI (Telegram) MCP server still maintained?
Better-TG-CLI (Telegram) is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Better-TG-CLI (Telegram) MCP server under?
Better-TG-CLI (Telegram) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.