Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.rixile9999/tdl-mcp

NPM · TDL-MCP

Read-only Telegram MCP server wrapping the tdl CLI: list chats, read messages, download media.

Available components

81 Trust /100

Last scanned (23 hours ago)

Scores higher than 68% of npm servers

Category Communication

Trust breakdown (7 categories)

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 Security98
  • 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
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to rixile9999/tdl-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 620 tokens (~124/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

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.

  • 16 Oct 26 81

    First indexed and scored.

Diagnostics

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/tdl-mcp@1.1.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 rixile9999/tdl-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/rixile9999/tdl-mcp/.github/workflows/release.yml@refs/tags/v1.1.0
Rekor log index 3273161166
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:cb6641e2ca593d1471599f721a2c5369c30b319b46f3e7e1092c985b271ac0016357b7bbe049f5867e134209ebfc413938548fe57f29a2a81bae98c0c

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~620 tokens

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 →

Tool Tokens
tg_chats ~99

List the Telegram dialogs (chats/channels/groups/users) visible to the logged-in session, as [{id, type, name, username}]. Use it to find the chat id or @username to pass as `chat` to tg_messages / tg_download. Optional `filter` does a case-insensitive substring match on name/username/id.

NameTypeReqDescription
filterstring–Case-insensitive substring to match against chat name, username or id

No output schema declared.

No examples provided.

tg_download ~186

Download media files from one chat (by id or @username) to a local directory and return the absolute paths of newly downloaded files. Use extensions (csv, e.g. 'xlsx,pdf') to fetch only certain file types; since_id for 'everything new after message X'; last_n for 'the latest N media messages' (default 100). Already-present files are skipped (--skip-same).

NameTypeReqDescription
chatstringyesChat id or @username/domain (as shown by tg_chats)
deststring–Destination directory (default ~/Downloads/telegram)
extensionsstring–Comma-separated file extensions to include, e.g. 'xlsx,pdf'
last_ninteger–How many recent media messages to consider (default 100)
since_idinteger–Only messages with id > since_id (overrides last_n)

No output schema declared.

No examples provided.

tg_download_url ~123

Download the media of specific Telegram messages given their t.me links (e.g. https://t.me/channel/123) and return the absolute paths of newly downloaded files. Use when you already have message links rather than a chat to scan. Already-present files are skipped (--skip-same).

NameTypeReqDescription
deststring–Destination directory (default ~/Downloads/telegram)
extensionsstring–Comma-separated file extensions to include, e.g. 'xlsx,pdf'
urlsarrayyesTelegram message links; each must start with https://t.me/

No output schema declared.

No examples provided.

tg_messages ~158

Export recent media messages from one chat (by id or @username) and return them as compact {id, date, file, text} objects — newest range exported via tdl. Use last_n for 'the last N media messages', or since_id to fetch only messages after a known message id (incremental reads). Read-only.

NameTypeReqDescription
chatstringyesChat id or @username/domain (as shown by tg_chats)
last_ninteger–How many recent media messages to export (default 50, max 500)
since_idinteger–Only messages with id > since_id (overrides last_n; for incremental reads)
with_textboolean–Include message text content (default true)

No output schema declared.

No examples provided.

tg_status ~54

Check whether the local tdl Telegram session is logged in and usable. Call this first if another tg_* tool fails or before starting Telegram work. Never errors — returns {logged_in:false, hint} when the session is missing.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.rixile9999/tdl-mcp server?

io.github.rixile9999/tdl-mcp runs locally as an npm package, launched with npx -y tdl-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · tdl-mcp

# add to Claude Code
claude mcp add rixile9999-tdl-mcp -- npx -y tdl-mcp
Common questions

What is the io.github.rixile9999/tdl-mcp server?

io.github.rixile9999/tdl-mcp is listed in the public MCP registry as io.github.rixile9999/tdl-mcp. Read-only Telegram MCP server wrapping the tdl CLI: list chats, read messages, download media. This page covers its npm package (tdl-mcp).

Is the io.github.rixile9999/tdl-mcp server safe to use?

io.github.rixile9999/tdl-mcp scores 81 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 io.github.rixile9999/tdl-mcp server expose?

io.github.rixile9999/tdl-mcp exposes 5 tools: tg_status, tg_chats, tg_messages, tg_download, tg_download_url. Their descriptions and schemas cost roughly 620 tokens of context every time the server is loaded.

Is the io.github.rixile9999/tdl-mcp server still maintained?

io.github.rixile9999/tdl-mcp 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 io.github.rixile9999/tdl-mcp server under?

io.github.rixile9999/tdl-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.