Analytics
mory.dev
Provides access to Google Trends data for analyzing search interest over time, by region, and related queries.
ENDPOINT 1
https://trendflow.mory.dev/mcp
MCP server metadata
- Name
- trendflow
- Version
- 0.1.0
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. To gather data efficiently: pass up to 5 comparison terms in a single get_interest_over_time call rather than one call per term. If you have more than 3 topics to research, you must call research_bulk (up to 10 topics per call) instead of calling research_trend or other tools once per topic — a research pass over many topics has a fixed tool-call budget, and calling one topic at a time will run out before you finish. research_bulk gives each topic the same full picture as research_trend, and topics remain independent in the response. All figures are normalized relative interest, never absolute search volume, and are only comparable within one result set. If a call returns "rate limited" or "busy", wait the indicated seconds and retry the same call rather than issuing more calls.
Known tools 8
search_topicsResolves 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-onlyget_interest_over_timeGet relative search interest for one or more terms over a historical period.
Inferred read-onlyget_trending_nowLists 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-onlyresearch_trendReturns 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-onlyresearch_bulkResearches 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.
Inferred read-onlyCONNECT 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 and is being refreshed.
mory.dev is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.