Skip to main content
Glama

Related Servers

Alternatives to steam-trends-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides Steam concurrent player trends as JSON, offering monthly player time series, growth rates across 3M/6M/12M/5Y windows, and live most-played feeds via a single REST endpoint, without needing a Steam Web API key.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying live cross-platform gaming market data — Steam players, Twitch/YouTube viewership, prices, discounts, hype, and the aggro metric — through 8 read-only tools for summaries, rankings, genre rollups, game details, and search.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables exploring Steam store reviews and community discussion threads with server-side filtering, temporal analysis, and metadata context for understanding player sentiment and feedback beyond store page noise.
      13
      19 npm
      1
      BSD 3-Clause
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to audit Steam store pages for algorithmic health, forecast sales cones with P10/P50/P90 scenarios, and retrieve genre benchmarks for indie game market analysis.
      3
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables personalized Steam game discovery by ranking the store against a player's playtime history and stated preferences, with tools to search games, inspect details and reviews, and explore taste profiles.
      10
      13 npm
      MIT

    TDQS

    A4.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct query type: get_growth handles point-to-point growth, get_time_series provides full historical series, and get_top_trends returns live top-trending boards. The descriptions explicitly cross-reference when to prefer one tool over another, so there is little risk of misselection.

    Naming Consistency5/5

    All three tool names follow the same get_<specific_noun> pattern using snake_case. The verb prefix is consistent and the object distinguishes the data shape clearly.

    Tool Count5/5

    Three tools is within the ideal 3-15 range and each one earns its place by covering a distinct data retrieval mode. No redundant or filler tools exist.

    Completeness4/5

    The set covers the core needs for this domain: historical series, growth calculations, and live trend boards. A minor gap is that there is no explicit tool for listing available sources or categories, though the descriptions mention them inline.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues