67
/ 100
5 days ago
glama

telegram-mcp

An MCP server that connects to a Telegram group chat, persists messages to a local SQLite database, and exposes tools to search, retrieve, and send messages via SSE.

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

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

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 1 credential: BOT_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// required environment variables
This server reads these from process.env. You'll be asked to provide them before it can run.
🔐 secretBOT_TOKENyour bot token
configCHAT_ID3. Find "chat": {"id": ...} in the response — that is your .
configDB_PATHexport =./messages.db # override the /data default for local dev
configPORT
// 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/davidphc-telegram-mcp-bot-1o4gle)](https://m8ven.ai/mcp/davidphc-telegram-mcp-bot-1o4gle)
commit: 429b6018614a3cad77dd1fe5d6866d996f021d64
code hash: 21ee8563dd948ae12cedfa50f6aac5f65da814118716719d4032db3784f0cead
verified: 6/19/2026, 10:51:42 AM
view raw JSON →