← Back to the index
Registry updated within 30 days · Local · npm

Secure Telegram New this week NEW

io.github.antonorlov/secure-telegram-mcp copy

Telegram MCP server: each AI client gets its own key, scoped to chosen chats. Read-only by default.

CategoryDev Tools
TransportLocal
Registry freshnessRegistry updated within 30 days
Version0.3.3
Distributionnpm

Install & connect

Install · npmnpx
$ npx -y secure-telegram-mcp

Publisher-declared package identifier. Verify current package, permissions and client configuration before running; execution has not been tested here.

Freshness

Updated this week

Last registry update 2d ago · published Nov 4, 2026.

Registry position over time

Where Secure Telegram sits in the freshest-first index, tracked daily — new to the tracked index since the prior run. position movement fills in as the index runs daily.

Current position#4115
Best position#4115
Since prior runNEW

About this server

Telegram MCP server: each AI client gets its own key, scoped to chosen chats. Read-only by default.

Local — runs on your machine over stdio (npx / uvx / docker / bundle). Indexed under Dev Tools, alongside 29351 other servers. Health is freshness-derived from the registry's last-update timestamp; this index does not run the server, so capabilities and tool lists live in the source repository.

More in Dev Tools 29352

Browse all 29351 in Dev Tools →
Published · Nov 4, 2026
Updated · Nov 4, 2026
Source · official Model Context Protocol registry