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
      100 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

      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

    • google-data-mcp

      ducnhd
      A
      license
      A
      quality
      B
      maintenance
      MCP server providing access to Google Trends, YouTube listings, Google Ads Transparency, and Google Play reviews via plain HTTP, with no API key required. It caches results and paces requests to work within Google's informal rate limits.
      7
      2
      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 14 tools

    Disambiguation4/5

    Most tools target distinct data sources (Trends time series, News, Wikipedia, Autocomplete, Geo). However, the discovery-oriented tools (aeo_opportunities, discover_topics, related_queries, mine_questions) all produce content angles/questions and genuinely overlap, forcing the agent to rely on descriptions to choose. Boundaries are mostly clear but not perfectly crisp.

    Naming Consistency4/5

    All names use consistent snake_case, which is good. There's a mild mix between verb_noun (mine_questions, suggest_keywords, list_categories, compare_keywords) and noun_phrase (interest_over_time, related_queries, trending_now, news_coverage), but the pattern is predictable and readable throughout.

    Tool Count5/5

    14 tools sits squarely in the well-scoped 3-15 range. Each tool maps to a distinct data source or analysis task (trends, news, wiki, autocomplete, geo, categories, status), so no tool feels redundant or padded.

    Completeness4/5

    The SEO/AEO research domain is well covered: trend direction, related queries/topics, questions, regional interest, categories, news, Wikipedia, and health status. Minor gaps exist (no direct cross-keyword or cross-region time comparison beyond compare_keywords/interest_by_region), but core workflows have no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources