# HasData Google Trends (remote · mcp.hasdata.com)

Google Trends interest over time, by region, and related queries and topics, as JSON.

- Trust score: 86/100 (high trust)
- Change this week: +47
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-16

## Components

- remote · `mcp.hasdata.com`: 86/100 (this document), [markdown](https://verifymcp.io/servers/com-hasdata-google-trends/mcp.md), [page](https://verifymcp.io/servers/com-hasdata-google-trends/mcp)
- npm · `@hasdata/google-trends-mcp`: 49/100, [markdown](https://verifymcp.io/servers/com-hasdata-google-trends/hasdata-google-trends-mcp.md), [page](https://verifymcp.io/servers/com-hasdata-google-trends/hasdata-google-trends-mcp)
- pypi · `hasdata-google-trends-mcp`: 34/100, [markdown](https://verifymcp.io/servers/com-hasdata-google-trends/hasdata-google-trends-mcp-2.md), [page](https://verifymcp.io/servers/com-hasdata-google-trends/hasdata-google-trends-mcp-2)

## Channel facts

- Endpoint: `https://mcp.hasdata.com/mcp?apis=google_trends`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.7`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-16.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1267 tokens (~211/item across 6 items; 1 tools + 5 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 HasData Google Trends MCP server?

HasData Google Trends is a hosted endpoint at https://mcp.hasdata.com/mcp?apis=google_trends, so there is nothing to install locally. 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 --transport http com-hasdata-google-trends 'https://mcp.hasdata.com/mcp?apis=google_trends'
```

### Cursor

```json
{
  "mcpServers": {
    "com-hasdata-google-trends": {
      "url": "https://mcp.hasdata.com/mcp?apis=google_trends"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-hasdata-google-trends": {
      "type": "http",
      "url": "https://mcp.hasdata.com/mcp?apis=google_trends"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-hasdata-google-trends]
url = "https://mcp.hasdata.com/mcp?apis=google_trends"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-hasdata-google-trends": {
      "type": "remote",
      "url": "https://mcp.hasdata.com/mcp?apis=google_trends",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-hasdata-google-trends --url 'https://mcp.hasdata.com/mcp?apis=google_trends' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-hasdata-google-trends:
    url: "https://mcp.hasdata.com/mcp?apis=google_trends"
```

### Netclaw

```json
{
  "McpServers": {
    "com-hasdata-google-trends": {
      "Transport": "http",
      "Url": "https://mcp.hasdata.com/mcp?apis=google_trends"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-hasdata-google-trends -t streamable-http -u 'https://mcp.hasdata.com/mcp?apis=google_trends'
```

### Other

```json
{
  "mcpServers": {
    "com-hasdata-google-trends": {
      "type": "http",
      "url": "https://mcp.hasdata.com/mcp?apis=google_trends"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-10-16 (score 86, +1)

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

### 2026-10-13 (score 85, +1)

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

### 2026-10-12 (score 84, +1)

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

### 2026-10-10 (score 83, +44)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Stability: unverified → 0.17
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: excellent
- [functional] First check of Schema quality: fail

### 2026-09-28 (score 39, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 39, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-22 (score 39)

First indexed and scored.

## MCP tools (1)

### `hasdata_google_trends_search_getTrendsData` (~837 tokens)

google_trends_search: GET /

Get Google Trends Data

Pulls Google Trends data for one or more queries with geo targeting, region granularity (country/subregion/metro/city), date range, category, time zone, Google property (web, images, news, shopping, YouTube), and dataType (timeseries, geoMap, relatedTopics, relatedQueries). Returns interest-over-time series, geo-level breakdowns, and rising/top related topics/queries with relative scores. Use for keyword/content strategy, demand forecasting, seasonality analysis, topic discovery, campaign timing, and adding live-trend signals to marketing or research agents.

Input parameters:

- `cat` (string): Category of the search term. The default value is 0 ("All categories"). Provide one exact documented value (1133 allowed), e.g. `0`, `3`.
- `dataType` (string): Defines the type of search to perform. Available options:   - `timeseries`: Interest over time (default). Accepts both single and multiple queries per search.   - `geoMap`: Interest by region. Accep…
- `date` (string): Defines a date range for the search. Available options: - `now 1-H`: Past hour - `now 4-H`: Past 4 hours - `now 1-d`: Past day - `now 7-d`: Past 7 days - `today 1-m`: Past 30 days - `today 3-m`: Pas…
- `geo` (string): Specifies the location for the search. Defaults to Worldwide if not set or empty. Provide one exact documented value (3517 allowed), e.g. `AF`, `AF-BDS`.
- `gprop` (string): Sorts results by a specific property. The default property is Web Search (applied when the gprop parameter is not set or empty). Available options:   - `images`: Image Search   - `news`: News Search…
- `q` (string, required): Specify the search term for which you want to retrieve trends data.
- `region` (string): Used to get more specific results when using "Interest by region" data type. Other data types do not accept this parameter. The default value depends on the geo location that is set. Available optio…
- `tz` (number): Defines a time zone offset in minutes. The default value is 420 (Pacific Daylight Time (PDT): UTC-7). The valid range for this parameter is from -1439 to 1439. To calculate the `tz` value for a spec…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-hasdata-google-trends/mcp#diagnostics

## Score history

- 2026-10-16: 86
- 2026-10-15: 85
- 2026-10-14: 85
- 2026-10-13: 85
- 2026-10-12: 84
- 2026-10-10: 83
- 2026-10-04: 39
- 2026-10-03: 39
- 2026-10-02: 39
- 2026-10-01: 39
- 2026-09-30: 39
- 2026-09-29: 39
- 2026-09-28: 39
- 2026-09-27: 39
- 2026-09-26: 39
- 2026-09-25: 39
- 2026-09-24: 39
- 2026-09-23: 39
- 2026-09-22: 39

## Common questions

### What is the HasData Google Trends MCP server?

HasData Google Trends is an MCP server listed in the public MCP registry as com.hasdata/google-trends. Google Trends interest over time, by region, and related queries and topics, as JSON. This page covers its hosted endpoint (https://mcp.hasdata.com/mcp?apis=google_trends).

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

HasData Google Trends scores 86 out of 100 on VerifyMCP. 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 HasData Google Trends MCP server expose?

HasData Google Trends exposes 1 tool: hasdata_google_trends_search_getTrendsData. Their descriptions and schemas cost roughly 837 tokens of context every time the server is loaded.

### Does the HasData Google Trends MCP server require authentication?

Yes. HasData Google Trends asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

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

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

## Links

- Remote endpoint: https://mcp.hasdata.com/mcp?apis=google_trends
- Authorisation metadata: https://mcp.hasdata.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/HasData/google-trends-mcp
- Website: https://hasdata.com/apis/google-trends-api
- Changelog RSS feed: https://verifymcp.io/servers/com-hasdata-google-trends/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-hasdata-google-trends/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-hasdata-google-trends/mcp