Analytics

mory.dev

Provides access to Google Trends data for analyzing search interest over time, by region, and related queries.

1 endpoint7 known toolsFirst detected August 17, 2026Last detected August 17, 2026

ENDPOINT 1

https://trendflow.mory.dev/mcp

No auth detected

MCP server metadata

Name: trendflow
Version: 0.1.0

Capabilities

tools.listChanged

Server instructions

Google Trends data: what people search for, how interest changes over time, where it is concentrated, and what is surging right now. When the user names an entity, call search_topics first and pass the returned topic id to the other tools — a topic covers every phrasing and translation of a concept and measures far more search activity than the literal string. All figures are normalized relative interest, never absolute search volume, and are only comparable within one result set.

Known tools 7

list_regions

Returns the geo codes Google Trends accepts.

Inferred read-only

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.

Inferred read-only

get_interest_over_time

Get relative search interest for one or more terms over a historical period.

Inferred read-only

get_interest_by_region

Break down search interest for one term by geography.

Inferred read-only

get_related_queries

Find the top and rising searches related to a term.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

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

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: trendflow
Remote MCP URL: https://trendflow.mory.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "trendflow": {
      "type": "http",
      "url": "https://trendflow.mory.dev/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "trendflow",
  "transport": "streamable-http",
  "url": "https://trendflow.mory.dev/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for mory.dev was fetched 2026-08-21T12:33:59.513Z.

Trust status Trusted

mory.dev is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.