Skip to main content
Glama
alamri-intel

Telegram OSINT

by alamri-intel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Telegram OSINT

No user-submitted related servers found.

    Related Servers

    • telegram-briefing-mcp

      zainbacchus
      A
      license
      Not graded
      quality
      D
      maintenance
      A read-only Telegram MCP server that retrieves messages from your DMs, groups, and channels, enabling Claude to generate executive briefings from Telegram conversations.
      MIT

    • Paperplane

      yripper
      A
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server that signs in to a personal Telegram account and mirrors chats into a local SQLite store, letting Claude read history, search messages, track chats awaiting replies, and draft or send responses. It also supports organizing conversations through folders, labels, archiving, muting, and step-by-step cleanup plans.
      120 npm
      MIT

    • tg-agent (Telegram → SQLite →

      WhiteBite
      F
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server that syncs only the Telegram chats, folders, and forum topics you explicitly mark (via Telegram folders or watch.py) into a local SQLite index using Telethon, then exposes 13 read-only tools to an agent. Enables listing watched topics with unread counts, fetching new messages since last read, paging and date-filtered history retrieval with context budgets, full-text search over years of history (SQLite FTS5/bm25), activity stats, link/mention extraction, digests, and extracted entities such as tasks, decisions, promises, and questions with overdue tracking — all through user-defined aliases. No tool writes to Telegram, keeping the integration strictly read-only.
      1
      -

    • telemcp

      ashtokalo
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that gives AI assistants read-only access to your personal Telegram account via MTProto, enforcing a whitelist of allowed chats and never marking messages as read.
      MIT

    • telegram-business-mcp

      OlegNickeshin
      A
      license
      Not graded
      quality
      A
      maintenance
      Lets MCP clients like ChatGPT Web and Claude Web read, search, and reply to your personal Telegram chats through the official Telegram Business API, using a self-hosted SQLite archive without MTProto sessions.
      3
      Apache 2.0

    • Telegram Agent for Codex

      Frejixxx
      A
      license
      Not graded
      quality
      D
      maintenance
      Privacy-first Telegram MCP server enabling maintainers to triage chats, inspect context, search messages, draft replies, and send authorized messages locally without a cloud relay.
      41 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 20 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources