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/LoneVertex/telegram-mcp-nextgenWrote 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/lonevertex/telegram-mcp-nextgen/telegram-mcp)<a href="https://agentmods.dev/mcp/lonevertex/telegram-mcp-nextgen/telegram-mcp"><img src="https://agentmods.dev/badge/mcp/lonevertex/telegram-mcp-nextgen/telegram-mcp/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/lonevertex/telegram-mcp-nextgen/telegram-mcp"><img src="https://agentmods.dev/badge/mcp/lonevertex/telegram-mcp-nextgen/telegram-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
telegram-mcp 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 1mo 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.
This is a copy
100% identical to telegram-mcp — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{ "telegram-mcp": { "command": "uvx", "args": [ "telegram-mcp" ] } }
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.
- 1mo ago First seen · 8 lines scan A c5d599884976
telegram-mcp is an MCP server published in the GitHub repository LoneVertex/telegram-mcp-nextgen (0 stars, last pushed 4d ago), licensed Apache-2.0. 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. It is 100% identical to telegram-mcp, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
tg-recall
MCP server "tg-recall" as configured in Rerowros/tg-recall. Runs locally from the tg-recall Python package.
telegram-mcp
Telegram MCP server: give AI tools direct access to your Telegram account. Runs locally from the telegram-mcp-jgalea Python package.
shadow-tg
Telegram channel tools for AI agents — read public channels, search, analyze engagement. No MTProto. Runs locally from the shadow-tg Python package.
telegram-allowlist-mcp
MCP server "telegram-allowlist-mcp" as configured in nskondratev/telegram-mcp. Runs locally from the telegram-allowlist-mcp Python package.
papertrade
MCP server "papertrade" as configured in ryanrodrigues25200525-svg/tradingcli. Runs mcp_server.py with python3. Needs 1 environment variable to run.
agent-crm
MCP server "agent-crm" as configured in clayton/agent-crm. Runs locally from the agent-crm Python package.