9seconds

    9seconds/mtg

    Highly opinionated MTPROTO proxy for Telegram

    backend
    mtproto
    mtproxy
    telegram
    Go
    MIT
    3.7K stars
    393 forks
    3.7K GitHub watchers
    Updated Nov 2, 2026
    View on GitHub

    Build with Backblaze B2

    SDKs, agent skills, IDE extensions, and reference pipelines from Backblaze Labs. All open source.

    Explore Backblaze Labs

    Loading star history...

    Where it stands

    Rank, growth pace and release cadence relative to everything GStars tracks.

    No releases in the last 90 days; the most recent was 209 days ago, with 29 contributors on GitHub.

    The biggest single-day gain in the last year, +54 stars on Mar 25, coincided with release v2.2.4.

    Use Cases & Benefits

    • Implements a minimal, highly opinionated MTPROTO proxy for Telegram to enable access in censored or restricted environments.
    • Offers resource-efficient operation with domain fronting and doppelganger TLS traffic emulation to evade censorship and detection.
    • Use for deploying a lightweight Telegram proxy on a VPS to bypass network censorship without complex user management.
    • Use for integrating with load balancers via proxy protocol v1/v2 to scale Telegram proxy infrastructure.
    • Use for embedding MTPROTO proxy functionality into Go applications requiring custom Telegram connectivity solutions.

    Should you depend on it?

    License terms, project hygiene and risks, from GitHub metadata and GStars' snapshots.

    License

    MIT

    Permissive: commercial use, modification and redistribution are allowed with attribution.

    Community files

    • README: present

    Watch-outs

    No watch-outs from GStars' checks.

    General guidance from repository metadata, not legal advice. How we score

    From the README

    Highly-opinionated (ex-bullshit-free) MTPROTO proxy for Telegram.

    If you use v1.0 or upgrade broke you proxy, please read the chapter Version 2

    If you want to have a proxy that supports adtag (possibility to promote a channel with a special Telegram bot), I recommend to use telemt project. v1 of mtg supports it but I do not see any reasonable point of using it: adtag requires communication via a fragile set of middle proxies, requires complex setup that must expose a public IPs, has lower bandwidth and latency.

    mtg idea is simple: minimal unbloated proxy that can handle a reasonable scale ~10-20k simultaneous connections, has no user management, but ticks all checkboxes related to its main intent: provide a way to use Telegram.

    There are several available proxies for Telegram MTPROTO available. Here are the most notable:

    You can use any of these. They work great and all implementations have feature parity now. This includes support of adtag, replay attack protection, domain fronting, faketls, and so on. mtg has a similar goal: to give a possibility to connect to Telegram in a restricted, censored environment. But it does it slightly differently in details that probably matter.

    Excerpt from the 9seconds/mtg README on GitHub (MIT license). © its authors.Read the full README on GitHub

    Daily snapshots

    Stars gained per day, and how forks and open issues moved, from GStars' daily snapshots

    Forks

    393+16

    Open issues

    21+1

    Compared with peers in Backend

    Fastest-growing repositories GStars tracks in this cohort for the week of Nov 1, by 7-day star growth

    9seconds/mtg compared with Backend repositories by stars, 7-day star growth, health score and last release
    RepositoryStars+7dHealthLast release
    anthropics/skills187.8K+2.9K15—
    DuarteSantos8/openGym19.7K+2.4K602 days ago
    shiyu-coder/Kronos47.0K+2.3K16—
    NationalSecurityAgency/ghidra98.2K+2.3K6414 days ago
    microsoft/VibeVoice56.0K+1.1K29—
    9seconds/mtg3.7K—34209 days ago
    Category median56.0K+2.3K29—

    Discover Repositories

    Search across tracked repositories by name or description