# Google Trends (npm · google-trends-mcp-server)

Google Trends interest over time, by region, and trending searches in 125 countries.

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `google-trends-mcp-server`: 71/100 (this document), [markdown](https://verifymcp.io/servers/dataxplore19-google-trends-mcp-server/google-trends-mcp-server.md), [page](https://verifymcp.io/servers/dataxplore19-google-trends-mcp-server/google-trends-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `google-trends-mcp-server`
- Version: `1.0.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 89/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects basic-ftp 5.3.1, reached via apify-client > proxy-agent > pac-proxy-agent > get-uri > basic-ftp. A fixed version is available.
  - No install/post-install scripts declared.
  - 47 of 145 dependencies flagged as unhealthy (1 deprecated).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 281 tokens (~140/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Google Trends MCP server?

Google Trends runs locally as an npm package, launched with npx -y google-trends-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add dataxplore19-google-trends-mcp-server -- npx -y google-trends-mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "dataxplore19-google-trends-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "google-trends-mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dataxplore19-google-trends-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "google-trends-mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dataxplore19-google-trends-mcp-server -- npx -y google-trends-mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dataxplore19-google-trends-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "google-trends-mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dataxplore19-google-trends-mcp-server --command npx --arg -y --arg google-trends-mcp-server
```

### Hermes

```yaml
mcp_servers:
  dataxplore19-google-trends-mcp-server:
    command: "npx"
    args: ["-y", "google-trends-mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "dataxplore19-google-trends-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "google-trends-mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dataxplore19-google-trends-mcp-server -t stdio -c npx -a -y google-trends-mcp-server
```

### Other

```json
{
  "mcpServers": {
    "dataxplore19-google-trends-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "google-trends-mcp-server"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 68, +15)

- [security regression] Tool safety: pass → unverified
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.03
- [functional] First check of Schema quality: unverified
- [functional] Package version: 1.0.0 → 1.0.1

### 2026-11-15 (score 53)

First indexed and scored.

## MCP tools (2)

### `get_interest_over_time` (~164 tokens)

Google Trends: interest over time

Get Google Trends search interest (0-100) over time for one keyword, optionally with interest by region (US states, regions of a country, or countries when worldwide). Use it to see if a topic is rising, find its peak, or compare seasons. Call once per keyword: each series is scaled 0-100 on its own peak.

Input parameters:

- `geo` (string): Country code like US, GB, FR, DE. Empty for worldwide
- `include_regions` (boolean): Also return interest by region (or by country when worldwide)
- `keyword` (string, required): One search term, e.g. "chatgpt" or "electric cars"
- `timeframe` (string): Period. Short periods give hourly points, long ones daily or weekly

### `get_trending_searches` (~117 tokens)

Google Trends: trending searches

Get what people are searching for right now on Google in a country: the trending searches of the last 4, 24, 48 or 168 hours, with search volume and related queries. Use it for news, content ideas or market monitoring.

Input parameters:

- `country` (string): Country code, e.g. US, GB, FR, DE, IN, BR, JP (125 countries)
- `hours` (string): Look-back window in hours
- `max_results` (integer): Number of trending searches to return

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/dataxplore19-google-trends-mcp-server/google-trends-mcp-server#diagnostics

## Score history

- 2026-11-21: 71
- 2026-11-20: 70
- 2026-11-19: 70
- 2026-11-18: 69
- 2026-11-17: 69
- 2026-11-16: 68
- 2026-11-15: 53

## Common questions

### What is the Google Trends MCP server?

Google Trends is an MCP server listed in the public MCP registry as io.github.dataxplore19/google-trends-mcp-server. Google Trends interest over time, by region, and trending searches in 125 countries. This page covers its npm package (google-trends-mcp-server).

### Is the Google Trends MCP server safe to use?

Google Trends scores 71 out of 100 on VerifyMCP. We recorded 3 known advisories against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Google Trends MCP server expose?

Google Trends exposes 2 tools: get_interest_over_time, get_trending_searches. Their descriptions and schemas cost roughly 281 tokens of context every time the server is loaded.

### Is the Google Trends MCP server still maintained?

Google Trends is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Google Trends MCP server under?

Google Trends declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Google Trends MCP server?

VerifyMCP ran 16 checks on Google Trends, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/google-trends-mcp-server
- Socket report: https://socket.dev/npm/package/google-trends-mcp-server
- Repository: https://github.com/dataxplore19/google-trends-mcp-server
- Website: https://apify.com/data_xplorer/google-trends-fast-scraper
- Changelog RSS feed: https://verifymcp.io/servers/dataxplore19-google-trends-mcp-server/google-trends-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/dataxplore19-google-trends-mcp-server/google-trends-mcp-server/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dataxplore19-google-trends-mcp-server/google-trends-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/dataxplore19-google-trends-mcp-server/google-trends-mcp-server
