Skip to content

TrendFlow MCP server

dev.mory/trendflowmory.devstreamable-httpv0.1.0Scanned

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

8 tools: 1 change things and 7 only read.

Tools: 0 delete, 0 irreversible, 1 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 8
  • Can send data out · 0
  • No findings

Sign-in required, no OAuth metadata. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the TrendFlow MCP server can do

The TrendFlow MCP server is published by mory.dev, a domain the MCP Registry verified. It has 8 tools. It can create or change data (1 tool: research_bulk), but cannot delete data. 7 tools only read.

8 tools bring in text other people can write (list_regions, search_topics, get_interest_over_time and 5 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Nov 11, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

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.Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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 7Show 7 read-only tools
  • get_interest_by_regionBreak down search interest for one term by geography.Reads text others writeNo findings

    Why it is in this group

    • The name "get_interest_by_region" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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.Reads text others writeNo findings

    Why it is in this group

    • The name "get_interest_over_time" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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.Reads text others writeNo findings

    Why it is in this group

    • The name "list_regions" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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…Reads text others writeNo findings

    Why it is in this group

    • The name "search_topics" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write8
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 18:52 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
402
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 402.

Posture changes

  1. Nov 13, 2026
    • HTTP status of an anonymous initialize: 200 to 402
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://trendflow.mory.dev/.well-known/oauth-protected-resource to none
    • Authorization servers: https://upbeat-mirage-87.authkit.app to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: yes to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 402; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 1 -> 0 (and 5 more).View diff
    • HTTP status of an anonymous initialize: 200 to 402
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://trendflow.mory.dev/.well-known/oauth-protected-resource to none
    • Authorization servers: https://upbeat-mirage-87.authkit.app to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: yes to not observed

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
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 or a way out, 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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as trendflow. Review it before you use it.

Capability tags behind 8 rules
  • mcp__trendflow__list_regions untrusted-input
  • mcp__trendflow__search_topics untrusted-input
  • mcp__trendflow__get_interest_over_time untrusted-input
  • mcp__trendflow__get_interest_by_region untrusted-input
  • mcp__trendflow__get_related_queries untrusted-input
  • mcp__trendflow__get_trending_now untrusted-input
  • mcp__trendflow__research_trend untrusted-input
  • mcp__trendflow__research_bulk untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.mory/trendflow/verify?hash=cc0221048260fa83f61069ec06ae2fa66fd98b47db5a065b08faf7c019b6006a" | jq -e '.changed == false'

Pinned hash cc0221048260, from Nov 11, 2026, 08:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.mory/trendflow/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.mory/trendflow
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.mory/trendflow.svg)](https://radar.anlyon.com/servers/dev.mory/trendflow)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:11 UTC.

TrendFlow MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the TrendFlow MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the TrendFlow MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the TrendFlow MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the TrendFlow MCP server have?

8 tools: 1 write, 7 read. research_bulk, list_regions, search_topics, get_interest_over_time, get_interest_by_region, get_related_queries, get_trending_now and research_trend.

Does the TrendFlow MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the TrendFlow MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the TrendFlow MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.