Back to MCP Trust Indexm8ven
58
/ 100
1 month ago
github_topic

telegram-api-mcp

Ultimate Telegram Bot API MCP server — full v9.6 coverage, meta-mode, rate limiting, circuit breaker. TypeScript.

→ timoncool/telegram-api-mcp· listed on github_topic
Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find.

Install from

GitHubGlama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Known vulnerabilities in dependencies: 2 critical, 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 1 credential: TELEGRAM_BOT_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 critical3 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@3.0.0GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

criticalvitest@3.0.0GHSA-9crc-q9x8-hgqq

Vitest allows Remote Code Execution when accessing a malicious website while Vitest API server is listening

high@modelcontextprotocol/sdk@1.12.0GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.12.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.12.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// required environment variables
This server reads these from process.env. You'll be asked to provide them before it can run.
configTELEGRAM_ALLOWED_UPLOAD_DIRS— No — Comma-separated allowed upload paths
🔐 secretTELEGRAM_BOT_TOKEN— claude mcp add telegram -- npx telegram-api-mcp -e =your_token
configTELEGRAM_CB_COOLDOWN— No 30000 Circuit breaker cooldown (ms)
configTELEGRAM_CB_THRESHOLD— No 5 Failures before circuit opens
configTELEGRAM_DEFAULT_CHAT_ID— "": "-1001234567890"
configTELEGRAM_DEFAULT_THREAD_ID— No — Default forum topic thread ID
configTELEGRAM_DOWNLOAD_DIR
configTELEGRAM_GLOBAL_RATE_LIMIT— No 30 Max requests/sec ([Telegram limit](https://core.telegram.org/bots/faq#my-bot-is-hitting-limits))
configTELEGRAM_MAX_FILE_SIZE— No 52428800 Max upload file size (50MB)
configTELEGRAM_MAX_RETRIES— No 3 Retry attempts on transient errors
configTELEGRAM_META_MODE— No false Use 2 meta-tools instead of 169
configTELEGRAM_PER_CHAT_RATE_LIMIT— No 20 Max messages/min per group ([Telegram limit](https://core.telegram.org/bots/faq#my-bot-is-hitting-limits))
// full audit trail
The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/timoncool-telegram-api-mcp-1852ec)](https://m8ven.ai/mcp/timoncool-telegram-api-mcp-1852ec)
commit: c9c65ec4ebc473777eb56f0f9053e1bec5a245d5
code hash: 1e02fcad8f7d085d559093c4604b12c4778702b603e6899f29b859dd9fc35d9f
verified: 6/15/2026, 1:10:36 PM
view raw JSON →