74
/ 100
22 days ago
glama
Telegram Bridge MCP
Connects AI assistants to Telegram bidirectionally, enabling any MCP-compatible client to send messages, receive voice replies, and run multiple concurrent agent sessions through a single bot.
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
🚨
Secret credentials may flow to a network call
1 flow detected: BOT_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
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.config
ALLOWED_USER_ID— "": "your-user-id"config
ALLOW_ALL_USERS🔐 secret
BOT_TOKEN— "": "your-token",config
HIJACK_NOTIFYconfig
MCP_BINDconfig
MCP_PORTconfig
PERSISTENT_ANIMATION_WARN_MSconfig
STT_HOSTconfig
TELEGRAM_MCP_DEBUGconfig
TMCP_DATA_DIRconfig
TTS_HOST— Any OpenAI-compatible /v1/audio/speech endpointconfig
TTS_VOICE// 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
[](https://m8ven.ai/mcp/electrified-cortex-telegram-bridge-mcp-4sd6me)commit: 9129309c9d79531f635d63b256fc2c3f77b033f8
code hash: f81b6e754a0e974ab0a9841374fdf083237b4c552cf02aede91fe3462f92b489
verified: 6/17/2026, 12:11:14 PM