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/nileshpatil6/telegram-slack-mcpWrote 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/nileshpatil6/telegram-slack-mcp/slack-slack)<a href="https://agentmods.dev/mcp/nileshpatil6/telegram-slack-mcp/slack-slack"><img src="https://agentmods.dev/badge/mcp/nileshpatil6/telegram-slack-mcp/slack-slack/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/nileshpatil6/telegram-slack-mcp/slack-slack"><img src="https://agentmods.dev/badge/mcp/nileshpatil6/telegram-slack-mcp/slack-slack.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
slack 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 10d 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
{
"slack": {
"command": "npx",
"args": [
"-y",
"telegram-slack-mcp",
"slack"
]
}
}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.
- 10d ago First seen · 10 lines scan A c019a214a021
slack is an MCP server published in the GitHub repository nileshpatil6/telegram-slack-mcp (0 stars, last pushed 10d 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
dynamic-telegram-bot-api-mcp
A dynamic, self-refreshing MCP gateway for the complete Telegram Bot API. Runs locally from the dynamic-telegram-bot-api-mcp npm package.
tdl-mcp
MCP server "tdl-mcp" as configured in rixile9999/tdl-mcp. Runs locally from the tdl-mcp npm package. Needs 2 environment variables to run.
tgread
MCP server "tgread" as configured in demian-overflow/tgread. Runs locally from the tgread Python package.
mcp-notify
MCP Server for notify. Runs locally from the mcp-notify Python package. Needs 11 environment variables to run.
telethon-plus
MCP server "telethon-plus" as configured in psyb0t/docker-telethon-plus. Runs in Docker (docker.io/psyb0t/telethon-plus:v0.5.7).
mcp-telegram-claudecode
MCP server for Telegram integration with Claude Code - Send and receive messages via Telegram. Runs locally from the mcp-telegram-claudecode npm package.