# Better-TG-CLI (Telegram) (npm · better-tg-cli)

Telegram on your own account: read, search, send and press bot buttons. Writes need your approval.

- Trust score: 89/100 (high trust)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-16

## Components

- npm · `better-tg-cli`: 89/100 (this document), [markdown](https://verifymcp.io/servers/thevilfer-better-tg-cli/better-tg-cli.md), [page](https://verifymcp.io/servers/thevilfer-better-tg-cli/better-tg-cli)

## Channel facts

- Registry: `npm`
- Package: `better-tg-cli`
- Version: `0.37.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-16.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to TheVilfer/better-tg-cli).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 317 tokens (~105/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 75/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 25% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add thevilfer-better-tg-cli -- npx -y better-tg-cli
```

### Cursor

```json
{
  "mcpServers": {
    "thevilfer-better-tg-cli": {
      "command": "npx",
      "args": [
        "-y",
        "better-tg-cli"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "thevilfer-better-tg-cli": {
      "command": "npx",
      "args": [
        "-y",
        "better-tg-cli"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add thevilfer-better-tg-cli -- npx -y better-tg-cli
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "thevilfer-better-tg-cli": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "better-tg-cli"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add thevilfer-better-tg-cli --command npx --arg -y --arg better-tg-cli
```

### Hermes

```yaml
mcp_servers:
  thevilfer-better-tg-cli:
    command: "npx"
    args: ["-y", "better-tg-cli"]
```

### Netclaw

```json
{
  "McpServers": {
    "thevilfer-better-tg-cli": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "better-tg-cli"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add thevilfer-better-tg-cli -t stdio -c npx -a -y better-tg-cli
```

### Other

```json
{
  "mcpServers": {
    "thevilfer-better-tg-cli": {
      "command": "npx",
      "args": [
        "-y",
        "better-tg-cli"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-14 (score 89, +39)

- [security improvement] Injection markers: unverified → pass
- [functional improvement] Stability: unverified → 0.57
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass

### 2026-10-12 (score 50, −34)

- [security regression] Stability: 0.23 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] 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

### 2026-10-04 (score 84, +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.

### 2026-10-02 (score 83, +27)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → pass

### 2026-10-01 (score 56, 0)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → pass
- [functional] Package version: 0.30.0 → 0.33.0
- [functional] Package version: 0.30.0 → 0.31.1

### 2026-09-30 (score 56, −26)

- [security regression] Malware scan: pass → unverified
- [security regression] Known CVEs: pass → unverified
- [functional regression] Dependency health: pass → unverified
- [functional] Package version: 0.28.0 → 0.30.0
- [functional] Package version: 0.28.0 → 0.29.0

### 2026-09-29 (score 82, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-28 (score 66, −3)

- [security regression] Malware scan: pass → unverified
- [security regression] Tool safety: pass → unverified
- [security improvement] 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.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Dependency health: unverified → pass
- [functional improvement] 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

## MCP tools (3)

### `telegram_help` (~42 tokens)

Telegram CLI reference

List telegram CLI commands and flags. Pass grep to filter (e.g. "thread", "search"). Call this before guessing flags.

Input parameters:

- `grep` (string)

### `telegram_read` (~103 tokens)

Read Telegram

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.

Input parameters:

- `args` (array, required)

### `telegram_write` (~102 tokens)

Write to Telegram

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.

Input parameters:

- `args` (array, required)
- `stdin` (string): Text for a "-" argument (message body), avoids quoting issues

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/thevilfer-better-tg-cli/better-tg-cli#diagnostics

## Score history

- 2026-10-16: 89
- 2026-10-15: 89
- 2026-10-14: 89
- 2026-10-13: 50
- 2026-10-12: 50
- 2026-10-04: 84
- 2026-10-03: 83
- 2026-10-02: 83
- 2026-10-01: 56
- 2026-09-30: 56
- 2026-09-29: 82
- 2026-09-28: 66
- 2026-09-27: 69

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/better-tg-cli
- Socket report: https://socket.dev/npm/package/better-tg-cli
- Repository: https://github.com/TheVilfer/better-tg-cli
- Changelog RSS feed: https://verifymcp.io/servers/thevilfer-better-tg-cli/better-tg-cli.xml
- Changelog JSON feed: https://verifymcp.io/servers/thevilfer-better-tg-cli/better-tg-cli.json
- HTML version of this page: https://verifymcp.io/servers/thevilfer-better-tg-cli/better-tg-cli