Skip to main content
Glama
Johnhyeon

TelegramLens

by Johnhyeon

Related Servers

Alternatives to TelegramLens

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server and background daemon that captures Discord and Telegram conversations locally to provide persistent memory for Claude Code sessions. It enables hybrid search and automatic context injection of chat history to maintain continuity across development sessions.
      3 npm
      22
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Unofficial MCP server providing Vietnamese stock market financial data, enabling natural language interaction with Claude Desktop.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Institutional Financial Intelligence MCP Server for Claude Desktop & AI Agents. Sub-second market data, technical indicators, SEC EDGAR 10-K parsing, and local SQLite backtesting.
      1
      MIT

    TDQS

    A3.9/5.0

    Scored across 23 tools

    Disambiguation3/5

    The set contains several overlapping analytics tools (telegram_trending, telegram_momentum, telegram_buzz_score, telegram_velocity, telegram_stock_buzz), and telegram_trending with sort_by='baseline_ratio' closely resembles telegram_momentum. However, the detailed descriptions and explicit routing instructions (e.g., stock-code matching vs telegram_search) help an agent distinguish most tools in practice.

    Naming Consistency4/5

    All tools share the consistent telegram_ prefix and snake_case format, which makes the set predictable. The internal style is not strictly verb_noun—telegram_velocity and telegram_momentum are noun-like while telegram_add_alias and telegram_send_me are verb-like—but this is a minor deviation rather than a chaotic mix.

    Tool Count3/5

    23 tools is on the heavy side for an agent-facing server and falls in the 16–25 borderline range. Many tools have distinct roles across collection, analytics, curation, and delivery, but the analytics cluster could likely be consolidated without significant capability loss.

    Completeness4/5

    The server covers the full Telegram stock-buzz workflow: collection/status/backfill, raw message search, ranking and stock-level analytics, channel classification/tiering, alias/blocklist curation, and user delivery. Minor gaps such as explicit channel add/remove and message-ID-level retrieval exist, but they are not central to the stated purpose and can be worked around.

    Maintenance

    ActivityActive
    ResponsivenessNo issues