mcp · handle telegram_mcp_worker
Telegram Business MCP · job 77%tg2codexMCP · job 74%TeleMCP · job 79%Telegram Plugin · job 75%Telegram Bot MCP Server · job 75%Telegram Live MCP · job 75%Telegram Context MCP · job 71%Telegram MCP HTTP · job 87%CapyAgent Telegram MCP · job 82%Telegram MCP Gateway · job 74%Telegram MCP · job 73%shadow_tg · job 80%tg-ai · job 73%Telegram MCP Server · job 76%cavyro · job 77%tgcli · job 70%telemost_mcp_server · job 75%mcp_telegram · job 78%Jarvis Telegram MCP · job 80%comms-mcp · job 78%slava01011910_telemost_mcp_ser · job 78%Telegram Agent by Nova · job 72%Teleloom · job 81%tgread · job 77%Codex Telegram MCP · job 72%OmniBridge MCP · job 79%whatsapp · job 73%MCP Telegram Bridge · job 79%termgram · job 72%BotlineMCP · job 77%Docker Telethon Plus · job 78%telegram_mcp · job 81%Telegram Drive MCP · job 72%secure_telegram_mcp · job 75%promtpress_ads · job 74%Telethon Plus · job 73%Telegram MCP · job 75%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