io.github.tolboy/telegram-mcp-tdlib

MCPcommunity
v1.17.0io.github.tolboyUnknownUpdated 5d agoGitHub

Local-first TDLib Telegram MCP server with 115 tools, account isolation and production guardrails.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
9GitHub stars
1Forks
5d agoLast update
Needs 1 credential before it runs
  • TDLIB_API_HASHAPI keyrequired

    Telegram API hash from my.telegram.org

  • TDLIB_PHONE_NUMBERAPI keyoptional

    Telegram phone number; omit after preparing a persisted session when using QR authentication

  • TDLIB_AUTH_CODEAPI keyoptional

    One-time Telegram login code for a fresh headless container

  • TDLIB_2FA_PASSWORDAPI keyoptional

    Telegram 2FA password when the account requires it

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.tolboy
LicenseUnknown
Version1.17.0
Sourcemcp-registry
GitHubtolboy/telegram-mcp-tdlib
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ CleanvHEAD · 1mo agoHow well does this scan work?
EvalsNone
IndexedJul 5, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source1mo ago

Forge read 0 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Local-first TDLib Telegram MCP server with 115 tools, account isolation and production guardrails.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.

Topics

Related in chat & messaging