Skip to main content
Glama
phalkmin

trendzeist-mcp

by phalkmin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to trendzeist-mcp

No user-submitted related servers found.

    Related Servers

    • google-trends-mcp

      purahmanian
      A
      license
      A
      quality
      D
      maintenance
      Provides free Google Trends data (interest over time, term comparison, related queries, trending now, regional breakdown) to MCP-compatible AI clients without needing an API key.
      5
      130 npm
      2
      MIT

    • google-search-trends-mcp

      trendsmcp-ai
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides Google Search trend data as an MCP tool, with historical series, growth percentages, and live trending searches, no scraping or rate limits.
      1
      MIT

    • Google Trends MCP Server

      mamrrez
      A
      license
      A
      quality
      A
      maintenance
      Enables Claude, Cursor, and other MCP clients to retrieve and analyze Google Trends data, including trending searches, interest over time and by region, related queries, seasonality, momentum, and share of search, without requiring an API key.
      32
      65 PyPI
      4
      MIT

    • Google Trends MCP

      jain-eshan
      A
      license
      A
      quality
      A
      maintenance
      Enables querying Google Trends data directly from conversational MCP clients, including search interest over time, related queries and topics, regional breakdowns, and trending searches, for market research without leaving the chat.
      11
      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.7/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools target a distinct data source or analysis (trending_now, interest_over_time, news_coverage, wiki_attention, seasonality, trend_history), and descriptions carefully explain when to use each. However, discover_topics and aeo_opportunities overlap substantially—both take 1-5 seeds, pull rising/top queries, cluster question-shaped searches, compute coverage and scores, and rank candidates—so an agent may struggle to choose between them for ideation vs AEO work. related_queries/related_topics also bleed into discover_topics' output.

    Naming Consistency4/5

    All names use snake_case consistently and are readable, with a mix of verb_noun (suggest_keywords, compare_keywords, mine_questions, discover_topics) and noun_phrase (related_queries, interest_over_time, trend_history) conventions. The style is uniform, though the verb-first pattern isn't universal and one tool carries a branded prefix (trendzeist_status).

    Tool Count4/5

    18 tools is slightly above the comfortable 3-15 band, but the server spans many genuinely different data sources (Google Trends, Autocomplete, News, Wikipedia) and analytical views (seasonality, channels, change detection), so each tool maps to a real capability. The main redundancy is the discover_topics/aeo_opportunities pair, which could arguably be merged.

    Completeness5/5

    The surface covers the full trend-research lifecycle: raw feeds (trending_now), keyword expansion (related_queries/topics, suggest_keywords, mine_questions), regional and temporal interest, seasonality, cross-channel growth, external sources (news, Wikipedia), multi-seed discovery/AEO scoring, change detection, and a local history archive, plus a health/status tool. No obvious dead ends for a read-only analytics domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources