Skip to main content
Glama
Sign In
news-volume-mcp

news-volume-mcp

by trendsmcp-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to news-volume-mcp

No user-submitted related servers found.

    Related Servers

    • newsapi-ai-mcp

      elcamino
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients such as Claude, Codex, Cursor, and OpenCode to search and retrieve news articles and clustered real-world events from roughly 150,000 sources worldwide, with tools for keyword/concept/location/date filtering, full-text lookup by URI or URL, entity name-to-URI resolution, token usage checks, and raw access to any newsapi.ai API endpoint. Results are returned as compact JSON to conserve context, and both local stdio and remote HTTP deployment are supported.
      7
      MIT

    • Trends MCP

      trendsmcp
      A
      license
      Not graded
      quality
      C
      maintenance
      Real-time trend data from Google Trends (Search, Images, News, Shopping), YouTube, TikTok, Reddit, Amazon, Wikipedia, npm, Steam, Spotify, X (Twitter), App Store, Google Play, web traffic, and news sentiment via one MCP connection. Works with Claude, Cursor, VS Code, Windsurf, ChatGPT, and any MCP-compatible AI.
      28
      MIT

    • Google Trends MCP Server

      mamrrez
      A
      license
      A
      quality
      B
      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
      48 PyPI
      4
      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

    A4.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: get_growth for point-to-point changes, get_time_series for full historical series, and get_top_trends for live boards. The descriptions actively cross-reference each other to prevent confusion.

    Naming Consistency5/5

    All three tools follow the same get_ prefix followed by a clear noun: get_growth, get_time_series, get_top_trends. The naming pattern is uniform and predictable.

    Tool Count5/5

    Three tools is a well-scoped size for this server's purpose. Each tool covers a distinct core query type with no redundancy.

    Completeness4/5

    The tool set covers growth, historical data, and live trends well. Minor gaps exist around multi-keyword time-series comparison and source/feed discovery, but agents can work around them.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Resources