Secure Telegram runs on your own machine — the client starts it, so there is no endpoint to ping. 291 installs a week from npm. Last commit 4 Nov 2026.
Telegram MCP server: each AI client gets its own key, scoped to chosen chats. Read-only by default.
What the code does
We read the source, 1 d ago · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
const child = spawn(
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found things in this code
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Secure Telegram and you get told the day something new turns up.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add secure-telegram-mcp -e 'TELEGRAM_MCP_ENDPOINT_TOKEN=<TELEGRAM_MCP_ENDPOINT_TOKEN>' -- npx -y secure-telegram-mcp{
"mcpServers": {
"secure-telegram-mcp": {
"command": "npx",
"args": [
"-y",
"secure-telegram-mcp"
],
"env": {
"TELEGRAM_MCP_ENDPOINT_TOKEN": "<TELEGRAM_MCP_ENDPOINT_TOKEN>"
}
}
}
}[mcp_servers.secure-telegram-mcp]
command = "npx"
args = ["-y", "secure-telegram-mcp"]
env = { TELEGRAM_MCP_ENDPOINT_TOKEN = "<TELEGRAM_MCP_ENDPOINT_TOKEN>" }{
"mcpServers": {
"secure-telegram-mcp": {
"command": "npx",
"args": [
"-y",
"secure-telegram-mcp"
],
"env": {
"TELEGRAM_MCP_ENDPOINT_TOKEN": "<TELEGRAM_MCP_ENDPOINT_TOKEN>"
}
}
}
}{
"servers": {
"secure-telegram-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"secure-telegram-mcp"
],
"env": {
"TELEGRAM_MCP_ENDPOINT_TOKEN": "<TELEGRAM_MCP_ENDPOINT_TOKEN>"
}
}
}
}Put your own value in place of
<TELEGRAM_MCP_ENDPOINT_TOKEN> (The endpoint's API key. Run 'npx secure-telegram-mcp setup' in a terminal first: it logs in to Telegram and prints the key once).
The author’s registry entry marks it as required.
Alternatives to Secure Telegram
same job, measured the same wayMCP server for MySQL. Read-only by default, row caps, statement timeouts, secrets never logged.
MCP server for MariaDB. Read-only by default, row caps, timeouts, secrets never logged.
MCP server for PostgreSQL. Read-only by default, row caps, timeouts, secrets never logged.
Read-only Keeper MSP posture across every client, with history, a change feed and no path to a
A secured scoped SSH MCP server for executing safe read-only diagnostic DevOps / SysOps commands
Read-only network & security recon tools (DNS, TLS, headers, CORS) for AI agents, each graded.
Secure read-only MCP server for Slack workspaces
Connect your AI clients to your MCP servers—securely managed in one place.
Secure Telegram — questions
Answers built from our own checks of this server.