Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

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

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

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

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "trendflow": {
      "type": "remote",
      "url": "https://trendflow.mory.dev/mcp",
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "trendflow": {
      "type": "http",
      "url": "https://trendflow.mory.dev/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=trendflow&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vdHJlbmRmbG93Lm1vcnkuZGV2L21jcCJ9"
}

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

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

extensions:
  "trendflow":
    enabled: true
    name: "trendflow"
    type: streamable_http
    uri: "https://trendflow.mory.dev/mcp"
    timeout: 300

Quality 89 / 100good

protocol88 · weight 25

pass
protocol.modernsupports 2026-07-28 (server/discover)
pass
protocol.statelessanswers without a session
pass
protocol.transportstreamable HTTP
warn
protocol.list_ttltools/list declares ttlMs 0, so clients re-fetch it on every use

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene86 · weight 30

pass
tools.descriptionsevery tool has a description
pass
tools.description_lengthdescriptions are concise
pass
tools.schemasevery tool has an object input schema
pass
tools.annotations8 of 8 tools declare readOnlyHint or destructiveHint
fail
tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: research_bulk (destructiveHint, idempotentHint); get_interest_over_time (destructiveHint, idempotentHint); get_related_queries (destructiveHint, idempotentHint); …
pass
tools.token_costabout 2,897 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability100 · weight 15

pass
stability.changesno tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

8 tools, about 2,897 tokens to load them all · tool set f6dbc0d832e3 · checked 2026-10-20 10:03 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 92 / 100

provenance85

liveness99

freshness85

hygiene100

+repository +dns-namespace +website +reachable +uptime-98% ~updated-65d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://trendflow.mory.dev/mcp` streamable-http	none	yes	98%	334 ms	2026-07-28	2026-10-20

Tools (8)

`get_interest_by_region`read-only	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`read-only	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.
`get_related_queries`read-only	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.
`get_trending_now`read-only	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.
`list_regions`read-only	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.
`research_bulk`read-only	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`read-only	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.
`search_topics`read-only	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.

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "dev.mory/trendflow",
  "title": "TrendFlow",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://trendflow.mory.dev/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "0.1.0",
  "repository": {
    "url": "https://github.com/dariomory/trendflow-js",
    "source": "github"
  },
  "websiteUrl": "https://trendflow.mory.dev/docs/mcp",
  "description": "Google Trends data: interest over time, by region, related queries, and trending now."
}