# Telegram MCP (pypi · n24q02m-telegram)

Telegram for AI agents: messages, chats, media, and contacts in bot and user-account modes.

- Trust score: 19/100 (low)
- Change this week: −15
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- oci · `docker.io/n24q02m/telegram`: 2/100, [markdown](https://verifymcp.io/servers/n24q02m-better-telegram-mcp/docker-io-n24q02m-telegram.md), [page](https://verifymcp.io/servers/n24q02m-better-telegram-mcp/docker-io-n24q02m-telegram)
- pypi · `n24q02m-telegram`: 19/100 (this document), [markdown](https://verifymcp.io/servers/n24q02m-better-telegram-mcp/n24q02m-telegram.md), [page](https://verifymcp.io/servers/n24q02m-better-telegram-mcp/n24q02m-telegram)

## Channel facts

- Registry: `pypi`
- Package: `n24q02m-telegram`
- Version: `4.23.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-11-04.

- **Supply Chain Security**: 48/100
  - Malware scan not yet available for this package.
  - Known CVEs were checked across the 42 of 45 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - Dependency health was assessed across the 42 of 45 dependencies we could resolve, so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 23/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 7 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.

**Unverified: 5 categories.** Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it.

## Install

### How do I install the Telegram MCP server?

Telegram MCP runs locally as a PyPI package, launched with uvx n24q02m-telegram. 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 n24q02m-better-telegram-mcp -- uvx n24q02m-telegram
```

### Cursor

```json
{
  "mcpServers": {
    "n24q02m-better-telegram-mcp": {
      "command": "uvx",
      "args": [
        "n24q02m-telegram"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "n24q02m-better-telegram-mcp": {
      "command": "uvx",
      "args": [
        "n24q02m-telegram"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add n24q02m-better-telegram-mcp -- uvx n24q02m-telegram
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "n24q02m-better-telegram-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "n24q02m-telegram"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add n24q02m-better-telegram-mcp --command uvx --arg n24q02m-telegram
```

### Hermes

```yaml
mcp_servers:
  n24q02m-better-telegram-mcp:
    command: "uvx"
    args: ["n24q02m-telegram"]
```

### Netclaw

```json
{
  "McpServers": {
    "n24q02m-better-telegram-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "n24q02m-telegram"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add n24q02m-better-telegram-mcp -t stdio -c uvx -a n24q02m-telegram
```

### Other

```json
{
  "mcpServers": {
    "n24q02m-better-telegram-mcp": {
      "command": "uvx",
      "args": [
        "n24q02m-telegram"
      ]
    }
  }
}
```

## 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-11-04 (score 19, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-03 (score 34, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-29 (score 19, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-28 (score 34, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-27 (score 19)

First indexed and scored.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/n24q02m-better-telegram-mcp/n24q02m-telegram#diagnostics

## Score history

- 2026-11-04: 19
- 2026-11-03: 34
- 2026-11-02: 19
- 2026-11-01: 19
- 2026-10-31: 19
- 2026-10-30: 19
- 2026-10-29: 19
- 2026-10-28: 34
- 2026-10-27: 19

## Common questions

### What is the Telegram MCP server?

Telegram MCP is listed in the public MCP registry as io.github.n24q02m/better-telegram-mcp. Telegram for AI agents: messages, chats, media, and contacts in bot and user-account modes. This page covers its PyPI package (n24q02m-telegram).

### Is the Telegram MCP server safe to use?

Telegram MCP scores 19 out of 100 on VerifyMCP. 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.

### Is the Telegram MCP server still maintained?

Telegram MCP is still listed as active in the MCP registry. We last reached this channel on 4 November 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 Telegram MCP server under?

Telegram MCP declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/n24q02m-telegram/
- Socket report: https://socket.dev/pypi/package/n24q02m-telegram
- Changelog RSS feed: https://verifymcp.io/servers/n24q02m-better-telegram-mcp/n24q02m-telegram.xml
- Changelog JSON feed: https://verifymcp.io/servers/n24q02m-better-telegram-mcp/n24q02m-telegram.json
- HTML version of this page: https://verifymcp.io/servers/n24q02m-better-telegram-mcp/n24q02m-telegram