Skip to main content
Glama
Sign In
Subito Monitoring

Subito Monitoring

by Alexxanddr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Subito Monitoring

No user-submitted related servers found.

    Related Servers

    • Avito Monitor MCP

      fisyuk
      F
      license
      Not graded
      quality
      D
      maintenance
      A remote MCP server that searches Avito for new classified ads, filtering by price and returning only previously unseen listings. Designed for scheduled monitoring via ChatGPT tasks.
      -

    • MarketTwits MCP

      yar822
      F
      license
      A
      quality
      C
      maintenance
      Local SQLite archive and MCP search service for the Telegram channel @markettwits, enabling users to query asset-specific twits by instrument and time range.
      1
      -

    • telegram-mcp

      davidphc
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that connects to a Telegram group chat, persists messages to a local SQLite database, and exposes tools to search, retrieve, and send messages via SSE.
      -

    • Unofficial Telegram MCP

      NickShtefan
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to read and search Telegram chats, fetch media, export messages, inspect channel analytics, build a local index, and prepare confirmed replies, sends, reactions, joins, and callback button presses across multiple accounts through one daemon.
      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

    B3.2/5.0

    Scored across 8 tools

    Disambiguation4/5

    list_watches and monitoring_status both report freshness/errors, creating some overlap, though one is explicitly unauthenticated and the other is authenticated with Telegram backlog. search_items is clearly immediate versus persistent watches, and pause/resume/update/delete are distinct lifecycle actions.

    Naming Consistency4/5

    Seven of eight tools follow a clear verb_noun pattern: list_watches, pause_watch, search_items, create_watch, update_watch, resume_watch, delete_watch. monitoring_status breaks the verb pattern as a noun phrase, but the overall convention remains readable and predictable.

    Tool Count5/5

    Eight tools is well-scoped for this domain, covering the full watch lifecycle, status inspection, and an immediate search path. Each tool has a clear role without obvious bloat.

    Completeness4/5

    The surface covers create/list/update/delete plus pause/resume and status for persistent searches, and list_watches exposes baseline and freshness state. A dedicated get_watch by ID is absent, but it is a minor gap agents can work around via list_watches.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources