mcp · handle telegram_mcp_gateway
Codex Telegram MCP · job 78%Telegram Business MCP · job 83%Teleloom · job 85%termgram · job 74%Docker Telethon Plus · job 78%telepath · job 75%shadow_tg · job 77%tg-ai · job 74%Ficiel MCP · job 77%whatsapp_mcp_server · job 73%Telegram Account MCP · job 75%soroka · job 71%Mysocial MCP · job 74%Telegram MCP HTTP · job 81%CapyAgent Telegram MCP · job 88%tgcli · job 82%Telethon Plus · job 72%secure_telegram_mcp · job 77%Telegram MCP · job 83%Telegram MCP Server · job 74%WhatsApp Bridge · job 74%slava01011910_telemost_mcp_ser · job 78%Telegram Agent by Nova · job 82%MCP Telegram Bridge · job 74%Telegram Live MCP · job 81%telegram_mcp · job 81%mcp_telegram · job 78%Telegram MCP · job 72%telemost_mcp_server · job 77%tg2codexMCP · job 73%Jarvis Telegram MCP · job 81%Telegram MCP · job 80%Telegram Context MCP · job 72%GhostPaw Telegram · job 79%tg-max-mcp · job 82%telegram-mcp-worker · job 74%Percentages are graph-similarity metadata, not suitability scores. A graph edge answers “is it connected” — plan fit and comparable cost are checked below.
Pick the exact reference and alternative series. Each history is separate; gaps stay gaps.
This view calls the same get_evidence tool your agent would — chart, table and MCP response describe the same records. Watch the reference series