Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/iamalexzatcepin/telegram-mcp-templateWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/iamalexzatcepin/telegram-mcp-template/telegram-mcp-telegram)<a href="https://agentmods.dev/mcp/iamalexzatcepin/telegram-mcp-template/telegram-mcp-telegram"><img src="https://agentmods.dev/badge/mcp/iamalexzatcepin/telegram-mcp-template/telegram-mcp-telegram/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/iamalexzatcepin/telegram-mcp-template/telegram-mcp-telegram"><img src="https://agentmods.dev/badge/mcp/iamalexzatcepin/telegram-mcp-template/telegram-mcp-telegram.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
telegram scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"telegram": {
"type": "stdio",
"command": "uv",
"args": [
"run",
"--project",
"./mcp_server",
"telegram-mcp",
"serve"
],
"cwd": "./",
"env_vars": [
"TELEGRAM_MCP_CONFIG",
"TELEGRAM_MCP_CONFIG_DIR",
"TELEGRAM_MCP_MASTER_KEY",
"TELEGRAM_MCP_CACHE_KEY",
"TELEGRAM_MCP_DOWNLOAD_DIR",
"TELEGRAM_MCP_UPLOAD_DIR",
"XDG_CONFIG_HOME"
],
"startup_timeout_sec": 20,
"tool_timeout_sec": 90
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 25 lines scan A b6ec7662297d
telegram is an MCP server published in the GitHub repository iamalexzatcepin/telegram-mcp-template (0 stars, last pushed 15d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
multisim-mcp
Unofficial MCP server for NI Multisim Automation API. Runs locally from the multisim-mcp Python package. Needs 1 environment variable to run.
raycast
Raycast workflow automation MCP server with 9 tools. Runs locally from the raycast-mcp-server npm package.
mailwarden
Native Gmail MCP server: search, labels, archive, trash, attachments, and snooze. Runs locally from the mailwarden npm package. Needs 4 environment variables to run.
habitica
MCP server "habitica" as configured in rodcordeiro/habitica-mcp. Runs ../../dist/index.js with node. Needs 3 environment variables to run.
pomodoro-ai-mcp
Pomodoro Ai MCP server. Tools: start session, stop session, get stats. Built by MEOK AI Labs. Runs locally from the pomodoro-ai-mcp Python package.
acuity-scheduling
Read appointments, types, calendars and availability; create, cancel or reschedule bookings. Remote server at acuity-scheduling.usefulapi.io.