Telegram OSINT
Related Servers
Alternatives to Telegram OSINT
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceConnects your own Telegram account or a bot to Claude and other AI assistants so they can read, search, send, and wait for Telegram messages, with everything stored in a local database.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code sessions to read, send, search, and watch Telegram chats and forum topics through a single always-on local daemon that keeps the only Telegram connection. Sending is governed by an editable rules file with blocked, approval, and auto-send lists, nickname resolution, and interactive approvals via a menu bar app, a Claude dialog, or a confirm tool.37 npm1MIT
- AlicenseNot gradedqualityDmaintenanceA read-only Telegram MCP server that retrieves messages from your DMs, groups, and channels, enabling Claude to generate executive briefings from Telegram conversations.MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to search and read a private, local archive of your own Telegram chats, groups and media, so they can answer questions about past conversations. It keeps access read-only toward Telegram, treats message text as untrusted, and lets you choose which chats AI apps may see.63MIT
- AlicenseNot gradedqualityBmaintenanceA read-only server that lets any MCP client or model list, search, and read your own Telegram chats, including chat details, forum topics, message history, and surrounding context. It never sends, edits, or deletes anything, and stores your Telegram credentials encrypted at rest.MIT
- AlicenseNot gradedqualityBmaintenanceAn open-source, read-only MCP server that connects your own Telegram account to ChatGPT, Claude and Claude Code via OAuth, enabling access to chats, message history, search, public channels and files with per-client scopes and revocable grants.Apache 2.0
TDQS
Scored across 20 tools
Each tool targets a distinct action/resource: auth flow (status, credentials, request/submit code), dialog reading, search, alert-rule CRUD, criterion CRUD, alert listing/acking, and a monitor status check. The two-tier design (rules prefilter, criteria judge, alerts result) is explicitly documented, so even similar-sounding pairs like list_alert_rules/list_alerts and set_alert_rule_enabled/set_criterion_enabled are clearly separated.
The vast majority follow a clean verb_noun pattern (list_alert_rules, add_alert_rule, delete_criterion, search_messages, ack_alerts). A few deviate to noun-phrases with no verb (auth_status, unread_summary, monitor_status), which is a minor inconsistency but still readable and predictable.
At 20 tools this is on the heavier side, but the surface spans several genuinely distinct concerns (auth, reading, rules, criteria, alerts, monitoring), and each tool maps to a real operation without obvious redundancy. It sits just above the ideal band rather than being bloated.
Coverage is strong: full login/auth flow, dialog listing, reading, searching, preview-before-create, and CRUD for both rules and criteria, plus alert listing/acking and daemon status. Minor gaps remain (no delete/prune or un-ack for alerts, no fetch-by-id), but these are workaroundable.