Skip to content

Google Trends MCP server

ai.trendsmcp/google-trendstrendsmcp.aistreamable-httpv1.0.7Scanned

Google Trends: Search, Images, News, Shopping over time, growth metrics. Free key at trendsmcp.ai

6 tools: 6 only read.

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

Tools listed without sign-in. Remote posture

Anlyon alternative

Run the operations that matter as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Google Trends MCP server can do

The Google Trends MCP server is published by trendsmcp.ai, a domain the MCP Registry verified. It has 6 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

5 tools bring in text other people can write (trends___get_context, trends___get_growth, trends___get_reviews and 2 more).

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

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 8, 2026, version 1.0.7.

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.

6 tools

Only reads 6Show 6 read-only tools

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 write5
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:25 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-03-26
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://google-trends.api.trendsmcp.ai/.well-known/oauth-protected-resource/mcp
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
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. Tools3 added, 1 removed, 3 changed.+3 added−1 removed~3 changedView diff

Install

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

claude mcp add --transport http google-trends https://google-trends.api.trendsmcp.ai/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http google-trends https://google-trends.api.trendsmcp.ai/mcp --header 'Authorization: <your-authorization>'

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__google-trends__trends___get_context",
      "mcp__google-trends__trends___get_growth",
      "mcp__google-trends__trends___get_reviews",
      "mcp__google-trends__trends___get_time_series",
      "mcp__google-trends__trends___get_top_trends",
      "mcp__google-trends__trends___get_usage"
    ],
    "ask": [],
    "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 google-trends. Review it before you use it.

Capability tags behind 5 rules
  • mcp__google-trends__trends___get_context untrusted-input
  • mcp__google-trends__trends___get_growth untrusted-input
  • mcp__google-trends__trends___get_reviews untrusted-input
  • mcp__google-trends__trends___get_time_series untrusted-input
  • mcp__google-trends__trends___get_top_trends 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/ai.trendsmcp/google-trends/verify?hash=167c28fee922854cc769c1aa532700c50e19fd9c63b412dcdc81167fa32f23d4" | jq -e '.changed == false'

Pinned hash 167c28fee922, from Nov 8, 2026, 06:18 UTC.

Watch

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

https://radar.anlyon.com/servers/ai.trendsmcp/google-trends/changes.xml

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

Badge

Anlyon Radar badge for ai.trendsmcp/google-trends
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.trendsmcp/google-trends.svg)](https://radar.anlyon.com/servers/ai.trendsmcp/google-trends)

Source: MCP Registry · repository. Synced Oct 21, 2026, 20:17 UTC.

Google Trends MCP server: questions and answers

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

Is the Google Trends MCP server safe?

No scan can promise that. What its definitions show: 6 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the Google Trends MCP server delete data?

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

Can the Google Trends 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 Google Trends MCP server have?

6 tools: 6 read. trends___get_context, trends___get_growth, trends___get_reviews, trends___get_time_series, trends___get_top_trends and trends___get_usage.

Does the Google Trends MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Google Trends MCP server send data to outside services?

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

Has the Google Trends MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.