TrendFlow MCP Server

by mory Your server? Claim it

answering

TrendFlow is answering right now. Last checked 6 min ago. It exposes 8 tools. Last commit 7 Sep 2026.

Google Trends data: interest over time, by region, related queries, and trending now.

Uptime history 62 days of history · worst day 0%

62 days agonow

82.6%

Uptime 24h

76 of 92 checks

Tools

read from the server

264 ms

Response time

average over 24h

Stars

last commit 7 Sep 2026

What changed 7

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 17 August 2026. No other catalogue keeps this.

18 Aug a tool appeared research_bulk

17 Aug 5 tools changed the parameters they ask for get_interest_by_region, get_interest_over_time, get_related_queries and 2 more

17 Aug a tool appeared list_regions

TrendFlow does not always answer

Over the last week it answered 54.9% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add trendflow --transport http https://trendflow.mory.dev/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "trendflow": {
      "url": "https://trendflow.mory.dev/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.trendflow]
url = "https://trendflow.mory.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "trendflow": {
      "url": "https://trendflow.mory.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "trendflow": {
      "url": "https://trendflow.mory.dev/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

interest

get_interest_by_region

Break down search interest for one term by geography. Use this when the user asks where something is popular, or wants a regional or city-level comparison. Values are normalized relative interest (0-100 within the result set).

get_interest_over_time

Get relative search interest for one or more terms over a historical period. Use this when the user asks how popular something is, whether it is rising or falling, or how several things compare — passing multiple keywords compares them on one scale. Values are normalized relative interest (0-100 within the result set), not absolute search volume.

research

research_bulk

Researches up to 10 topics in a single call, each with the same full picture as `research_trend`: interest over time, where it is most searched, and related queries. Each topic is looked up on its own scale, so they are not comparable to one another. Use this when you need data across many topics — a long or rich research pass — instead of one tool call per topic. Each section is fetched independently, so a partial result is normal: any section that fails carries an `error` instead of data and the rest still returns.

research_trend

Returns a full picture of one term in a single call: interest over time, where it is most searched, and the queries people search alongside it. Suited to open-ended research on a topic rather than one narrow question. Each section is fetched independently, so a partial result is normal: any section that fails carries an `error` instead of data and the rest still returns.

regions

list_regions

Returns the geo codes Google Trends accepts. With no argument it lists every country; given a country code it lists that country's sub-regions — US states, German states, UK nations — each as a code and a name. Any code returned here can be passed as the `region` argument of the other tools.

get_related_queries

Find the top and rising searches related to a term. Use this for keyword discovery, SEO and content research, and spotting breakout queries. `top` is ranked by volume; `rising` is ranked by growth, where "Breakout" means growth too large to measure.

topics

search_topics

Resolves a name — a company, product, person, technology, or concept — to its Google Trends topic id (`mid`), with a `type` field that distinguishes same-name entities such as Nike the company from Nike the goddess. A topic aggregates every spelling and translation of one concept, so it measures considerably more search activity than a literal phrase: the topic for "artificial intelligence" scores 62 where the literal string scores 1. The other TrendFlow tools accept a topic id anywhere they accept a keyword.

trending

get_trending_now

Lists the searches surging right now in a country, for questions about what is spiking without a term being named, and for news and real-time context. The `backend` parameter selects the source: "rpc" returns around 50 entries with growth percentages and a relative volume index; "rss" returns 10 entries together with the news articles behind each one; "auto" tries rpc and falls back to rss.

Endpoints

URL	Transport	State	Latency	Checked
https://trendflow.mory.dev/mcp	streamable-http	answering	257 ms	6 min ago

Alternatives to TrendFlow

same job, measured the same way

Google Trends API

by saulius876-lgtm

Google Trends in bulk: interest over time, by region, related and rising queries, trending now.

answering

Google Trends Scraper API - Interest Over Time, Related Queries

by anshumanatrey

Google Trends Scraper API: Interest and Trending Now

answering

HasData Google Trends

by hasdata

Google Trends interest over time, by region, and related queries and topics, as JSON.

305 installs/wk 1 tools answering

Google Trends Scraper

by fernandoguiraud16-coder

Google Trends interest over time and by region, rising queries and trending searches.

answering

Google Trends

by mamrrez

Google Trends: Trending Now, interest over time, regions, related searches. No API key.

176 installs/wk local only

Google Trends (via Apify)

by retracn

Google Trends data for AI agents: interest over time, regions, rising queries and trending searches.

answering

Google Trends MCP

by purahmanian

Google Trends MCP server: interest over time, comparisons, related queries, trending searches

188 installs/wk local only

Google Trends API: Bulk Trend Summaries

by meridianlabssoftware

Bulk Google Trends: interest over time, regions, rising queries and plain-English trend summaries.

answering

TrendFlow — questions

Answers built from our own checks of this server.

What can TrendFlow do?

It exposes 8 tools, read directly from the server on our last check. Among them: get_interest_by_region, get_interest_over_time, get_related_queries, get_trending_now, list_regions, research_bulk and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is TrendFlow mostly used for?

Its tools cluster around research and interest. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is TrendFlow working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 76 of 92 checks got a reply (82.6%), average response time 264 ms. The bar chart above shows every period we have measured.

How do I connect TrendFlow?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does TrendFlow need an API key?

No. TrendFlow completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is TrendFlow?

It answers our handshake in 264 ms on average, which is faster than 49% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is TrendFlow open source?

Yes — it is published under the MIT licence, written in TypeScript and 2 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.