mcp · handle telegram_go_mcp
telegram_mcp · job 83%Telegram Context MCP · job 79%CapyAgent Telegram MCP · job 74%Telegram Personal MCP · job 74%Telegram Drive MCP · job 78%tg-ai · job 81%Dotiphant · job 80%TeleMCP · job 78%Sherlock for Telegram · job 78%assistantctl · job 76%Telegram Bot MCP Server · job 81%Teleloom · job 74%Telegram Assistant MCP · job 76%mcp-telegram-agent · job 75%Telegram OSINT · job 82%tgread · job 76%Claude Messenger · job 75%Jarvis Telegram MCP · job 79%mcp_telegram · job 77%Telegram MCP · job 84%tg-ml-archive · job 73%shadow_tg · job 75%whatzmcp · job 72%whatsapp_mcp · job 75%Telegram Plugin · job 82%BotlineMCP · job 74%tgmarket · job 73%mcp-server-telegram-bot · job 77%AwrAIter · job 73%Telegram MCP Server · job 75%secure_telegram_mcp · job 74%mcpmessage · job 72%GPT History MCP · job 72%TgPilot · job 74%Wagent · job 71%better-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