Skip to content

TrendFlow

by mory.dev · remote · no sign-in to list tools · v0.1.0 · published by dev.mory

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

Changes · 1
CompareRegistry entry

8 tools: 1 change things and 7 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

8 tools

Changes things 1Claude Code: ask
  • research_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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
Only reads 7Claude Code: allow
  • get_interest_by_regionBreak down search interest for one term by geography.No findings

    Why it is in this group

    • The name "get_interest_by_region" says "get": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • get_interest_over_timeGet relative search interest for one or more terms over a historical period.No findings

    Why it is in this group

    • The name "get_interest_over_time" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • list_regionsReturns the geo codes Google Trends accepts.No findings

    Why it is in this group

    • The name "list_regions" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • research_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.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • 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…No findings

    Why it is in this group

    • The name "search_topics" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__trendflow__list_regions",
      "mcp__trendflow__search_topics",
      "mcp__trendflow__get_interest_over_time",
      "mcp__trendflow__get_interest_by_region",
      "mcp__trendflow__get_related_queries",
      "mcp__trendflow__get_trending_now",
      "mcp__trendflow__research_trend"
    ],
    "ask": [
      "mcp__trendflow__research_bulk"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as trendflow. Review it before you use it.