TrendFlow
REMOTE · TRENDFLOW.MORY.DEV · SCANNED AUG 20
Google Trends data: interest over time, by region, related queries, and trending now.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1909 tokens (~238/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability check failed: schema churn in the 4 days we've observed: 0 tool removals, 0 breaking changes, 1 auth/transport breaks, 2 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · trendflow.mory.dev
claude mcp add --transport http dev-mory-trendflow https://trendflow.mory.dev/mcp
[mcp_servers.dev-mory-trendflow] url = "https://trendflow.mory.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-mory-trendflow": {
"type": "remote",
"url": "https://trendflow.mory.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-mory-trendflow --url https://trendflow.mory.dev/mcp --transport streamable-http
mcp_servers:
dev-mory-trendflow:
url: "https://trendflow.mory.dev/mcp" {
"mcpServers": {
"dev-mory-trendflow": {
"type": "http",
"url": "https://trendflow.mory.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Aug 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 152 → 238 ▼ functional
- New tool “list_regions” functional
- New tool “research_bulk” functional
- “get_interest_by_region” added an optional parameter “category” cosmetic
- “get_interest_by_region” added an optional parameter “searchProperty” cosmetic
- “get_interest_by_region” added an optional parameter “timeframe” cosmetic
- “get_interest_over_time” added an optional parameter “category” cosmetic
- “get_interest_over_time” added an optional parameter “searchProperty” cosmetic
- “get_related_queries” added an optional parameter “category” cosmetic
- “get_related_queries” added an optional parameter “region” cosmetic
- “get_related_queries” added an optional parameter “searchProperty” cosmetic
- “get_related_queries” added an optional parameter “timeframe” cosmetic
- “get_interest_by_region” reworded the description of “region” cosmetic
- “get_interest_over_time” reworded the description of “region” cosmetic
- “get_interest_over_time” reworded the description of “timeframe” cosmetic
- “get_trending_now” reworded the description of “region” cosmetic
- “research_trend” reworded the description of “region” cosmetic
- 17 Aug 26 −13
- Stability: unverified → fail ▼ security
- Authorization: pass → unverified ▼ security
- 16 Aug 26 78
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Aug 2026 · Probed https://trendflow.mory.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.mory.dev | CN=YR1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | RSA 2048 | SHA256-RSA | 5161475cf4b39156f63585249c1f9af2538 |
| SANs: *.mory.dev, mory.dev | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of trendflow.mory.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| mory.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://trendflow.mory.dev/mcp | Verified | 200 | |
| http (plaintext) | http://trendflow.mory.dev/mcp | HTTPS enforced | 308 | https://trendflow.mory.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
get_interest_by_region Interest by region ~292
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).
| Name | Type | Req | Description |
|---|---|---|---|
| category | integer | – | Google Trends category id to restrict the query to; 0, the default, is every category. Narrowing disambiguates a word with several meanings without needing a topic id. |
| keyword | string | yes | A search term, or a topic id from search_topics (e.g. "/m/0mkz"). |
| region | – | – | Country code such as "US", "GB", "TH"; a sub-region such as "US-CA"; or a US metro code such as "807". Empty string means worldwide. |
| resolution | string | – | Geographic granularity of the breakdown. |
| searchProperty | string | – | Which Google surface to measure: empty for web search, or images, news, youtube, or froogle (Shopping). These are separate indexes, so values from different properties are not comparable to each othe… |
| timeframe | – | – | Time range. A preset, or a custom range as two ISO dates: "2023-01-01 2023-06-30". The range also sets granularity — hourly ranges return minute-level points and "all" returns monthly ones, so a long… |
No output schema declared.
No examples provided.
get_interest_over_time Interest over time ~319
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | integer | – | Google Trends category id to restrict the query to; 0, the default, is every category. Narrowing disambiguates a word with several meanings without needing a topic id. |
| keywords | array | yes | 1-5 search terms. Pass several to compare them against each other. Accepts topic ids from search_topics (e.g. "/m/0mkz") as well as literal phrases. |
| region | – | – | Country code such as "US", "GB", "TH"; a sub-region such as "US-CA"; or a US metro code such as "807". Empty string means worldwide. |
| searchProperty | string | – | Which Google surface to measure: empty for web search, or images, news, youtube, or froogle (Shopping). These are separate indexes, so values from different properties are not comparable to each othe… |
| timeframe | – | – | Time range. A preset, or a custom range as two ISO dates: "2023-01-01 2023-06-30". The range also sets granularity — hourly ranges return minute-level points and "all" returns monthly ones, so a long… |
No output schema declared.
No examples provided.
get_related_queries Related queries ~290
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | integer | – | Google Trends category id to restrict the query to; 0, the default, is every category. Narrowing disambiguates a word with several meanings without needing a topic id. |
| keyword | string | yes | A search term, or a topic id from search_topics (e.g. "/m/0mkz"). |
| region | – | – | Country code such as "US", "GB", "TH"; a sub-region such as "US-CA"; or a US metro code such as "807". Empty string means worldwide. |
| searchProperty | string | – | Which Google surface to measure: empty for web search, or images, news, youtube, or froogle (Shopping). These are separate indexes, so values from different properties are not comparable to each othe… |
| timeframe | – | – | Time range. A preset, or a custom range as two ISO dates: "2023-01-01 2023-06-30". The range also sets granularity — hourly ranges return minute-level points and "all" returns monthly ones, so a long… |
No output schema declared.
No examples provided.
get_trending_now Trending now ~196
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.
| Name | Type | Req | Description |
|---|---|---|---|
| backend | string | – | Source to use. "rpc" returns ~50 items with growth percentages; "rss" returns 10 with the news articles behind each trend; "auto" tries rpc then falls back to rss. |
| limit | integer | – | Maximum number of results to return. |
| region | – | – | Country code such as "US", "GB", "TH"; a sub-region such as "US-CA"; or a US metro code such as "807". Empty string means worldwide. |
No output schema declared.
No examples provided.
list_regions List regions ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | – | – | Country code such as "US", "GB", "TH"; a sub-region such as "US-CA"; or a US metro code such as "807". Empty string means worldwide. |
No output schema declared.
No examples provided.
research_bulk Research many trends ~220
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.
| Name | Type | Req | Description |
|---|---|---|---|
| region | – | – | Country code such as "US", "GB", "TH"; a sub-region such as "US-CA"; or a US metro code such as "807". Empty string means worldwide. |
| topics | array | yes | 1-10 topics (terms or topic ids) to research. Each is looked up on its own scale, so they are not comparable to one another. Use this to gather data across many topics in one call instead of one tool… |
No output schema declared.
No examples provided.
research_trend Research a trend ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | A search term, or a topic id from search_topics (e.g. "/m/0mkz"). |
| region | – | – | Country code such as "US", "GB", "TH"; a sub-region such as "US-CA"; or a US metro code such as "807". Empty string means worldwide. |
No output schema declared.
No examples provided.
search_topics Search topics ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A search term, or a topic id from search_topics (e.g. "/m/0mkz"). |
No output schema declared.
No examples provided.