by chaindead · MCP Server · ★ 350
Last updated: · Indexed by AgentSkillsHub · Auto-synced every 8h
brew install chaindead/tap/telegram-mcp
npx -y @chaindead/telegram-mcp
Taken from the project's README on GitHub.
Flagged: sudo usage. Scanned against 44 published rules built on the SlowMist agent-security taxonomy, refreshed every 8 hours.
The quality score combines nine heuristic checks of the repo and its README: completeness, clarity, specificity, examples, structure, agent readiness, step-by-step content, instruction quality and security notes. It rates how well the project explains itself to an agent, not the code.
| Stars | 350 |
| Forks | 58 |
| Language | Go |
| Category | MCP Server |
| License | MIT |
| Quality Score | 80/100 |
| Open Issues | 12 |
| Last Updated | 2026-05-28 |
| Created | 2025-04-01 |
| Platforms | go, mcp |
| Est. Tokens | ~4k |
Telegram MCP server The server is a bridge between the Telegram API and the AI assistants and is based on the Model Context Protocol. [!IMPORTANT] Ensure that you have read and understood the Telegram API Terms of Service before using this server. Any misuse of the Telegram API may result in the suspension of your account.
These tools work well together with telegram-mcp for enhanced workflows:
Looking for a telegram-mcp alternative? If you're comparing telegram-mcp with other mcp server tools, these 6 projects are the closest alternatives on Agent Skills Hub — ranked by topic overlap, star count, and community traction.
Telegram MCP server: connect your personal Telegram account to Claude, ChatGPT, Cursor and any MCP client. 182
MCP Server for Telegram
Rent the model. Own everything else. Free, open-source AI app for real work.
24 cross-platform agent skills for Claude Code, Cursor, Codex & Gemini CLI — databases, messaging, research, T
CLI for Telegram — agent-friendly, daemon-based, with webhook event push.
An open-source Python Telegram bot to transmit Telegram files over HTTP.
Explore other popular mcp server tools:
Grades come from a rule-based scan built on the SlowMist agent-security taxonomy: 44 published rules, covering credential harvesting, data exfiltration, curl | sh installers and more. It is a first-layer scan, not a manual audit — we say so rather than overstate it.
The scale of the problem is documented independently: Liu et al. (2026), in a study of 31,132 agent skills, report that 26.1% contain security vulnerabilities. Our own full-catalog census is published as a citable open dataset.
Sources & who's responsible: