Skip to main content
Glama
ra1nzzz

stepwork-hotspot-mcp

by ra1nzzz

Related Servers

Alternatives to stepwork-hotspot-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that connects to a WhatsHot Backend over HTTP to provide hot topic discovery, trend analysis, and historical data tools such as current hotlists, trend series, and event analysis.
      MIT
    • A
      license
      B
      quality
      F
      maintenance
      One-stop aggregation service of hot trends across the entire network based on the Model Context Protocol (MCP) protocol, supporting real-time updates and multi-data source expansion.
      21
      2
      Apache 2.0
    • F
      license
      B
      quality
      B
      maintenance
      WhatsHot MCP server aggregates trending hotlists, real-time news flashes, gold prices, and RSS feeds from 330+ sources, offering read-only tools to list sources, fetch current data, and query historical search and trend data via DuckDB.
      7
      3
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides hosted trend data MCP server for querying Google, TikTok, Amazon, Reddit, YouTube, Steam, npm and 30+ trend sources in natural language from any MCP-compatible AI.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides an AI-powered news aggregation and trend monitoring service, enabling multi-platform hotspot aggregation, RSS subscriptions, keyword filtering, AI translation, analysis briefs, and smart alerts delivered to various channels, all accessible through natural language via MCP.
      27
      1
      GPL 3.0

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one enumerates available sources with metadata, the other fetches actual hotspot entries with filtering and deduplication. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tool names follow a consistent verb_noun pattern (list_sources, discover_hotspots), using snake_case and clear action-resource structure. The naming is predictable and uniform.

    Tool Count3/5

    With only two tools, the server feels thin for a domain that might benefit from additional operations like source management or detailed retrieval. However, the two tools cover a focused workflow, making it borderline rather than severely under-scoped.

    Completeness4/5

    The core workflow of discovering hotspots from listed sources is covered. Minor gaps exist, such as the lack of tools to modify sources or fetch individual hotspot details, but these are not critical for the primary use case.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues