mcpdirectory.dev
9,129 servers · updated 23 Sept

Trendpulse MCP server

community Active last commit today
{
  "mcpServers": {
    "akzar1el-trendpulse": {
      "command": "uvx",
      "args": [
        "mcp-trendpulse"
      ],
      "env": {
        "TRENDPULSE_HTTP_PATH": "/path/to/directory"
      }
    }
  }
}
file .mcp.json (in your project root)install uvx mcp-trendpulseversion 0.2.11

What it does

TrendPulse is an MCP server that retrieves current news from Google News and analyzes search interest trends via Google Trends. It is for developers and researchers who need to incorporate live trending data and news context into their applications and workflows.

  • Search Google News by keyword, location, or publisher and extract article content to understand current coverage of a topic.
  • Retrieve interest-over-time data for keywords across geographic markets and calculate growth rates over custom time windows.
  • Discover related search queries and topics to explore keyword demand and identify related trending terms in a market.

Tools this server exposes

ToolDoes
search_google_newsSearch Google News by keyword, location, topic, or publisher domain to retrieve top news stories.
resolve_and_extract_articleExtract article content from Google News links with fallback to Playwright for difficult pages.
summarize_articleSummarize article text with optional MCP client sampling and local NLP fallback.
get_trending_termsRetrieve current trending terms for a specified geographic market.
get_interest_over_timePull Google Trends interest-over-time data for one or more keywords with custom time window analysis.
rank_trendsRank live trends by volume or growth metrics.
get_regional_interestInspect interest by country, region, city, or DMA where supported.
get_related_queriesExplore related queries, related topics, suggestions, and category IDs for a keyword.
compare_search_propertiesCompare Google Search, YouTube Search, News Search, Image Search, and Shopping trend properties.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.