# io.github.CloudCorpRecords/trenddata (oci · ghcr.io/cloudcorprecords/trenddata)

Google Trends data as JSON: interest over time, geo breakdowns and related queries.

- Trust score: 43/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@reneturcios/trenddata`: 67/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-trenddata/reneturcios-trenddata.md), [page](https://verifymcp.io/servers/cloudcorprecords-trenddata/reneturcios-trenddata)
- oci · `ghcr.io/cloudcorprecords/trenddata`: 43/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-trenddata/ghcr-io-cloudcorprecords-trenddata.md), [page](https://verifymcp.io/servers/cloudcorprecords-trenddata/ghcr-io-cloudcorprecords-trenddata)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/trenddata`
- Version: `0.1.0`
- 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**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **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 10 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 837 tokens (~837/item across 1 items; 1 tools + 0 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 1 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.CloudCorpRecords/trenddata MCP server?

io.github.CloudCorpRecords/trenddata runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/trenddata:0.1.0 mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-trenddata -- docker run --rm -i ghcr.io/cloudcorprecords/trenddata:0.1.0 mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-trenddata": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/trenddata:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-trenddata": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/trenddata:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-trenddata -- docker run --rm -i ghcr.io/cloudcorprecords/trenddata:0.1.0 mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-trenddata": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/trenddata:0.1.0",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-trenddata:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/trenddata:0.1.0", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-trenddata": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/trenddata:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-trenddata": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/trenddata:0.1.0",
        "mcp"
      ]
    }
  }
}
```

## 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 43, +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-11-19 (score 42, +1)

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

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

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 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-11-15 (score 40, +1)

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

### 2026-11-13 (score 39, +1)

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

### 2026-11-11 (score 38, +1)

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

### 2026-11-10 (score 37)

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: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-trenddata/ghcr-io-cloudcorprecords-trenddata#diagnostics

## Score history

- 2026-11-21: 43
- 2026-11-20: 42
- 2026-11-19: 42
- 2026-11-18: 41
- 2026-11-17: 41
- 2026-11-16: 40
- 2026-11-15: 40
- 2026-11-14: 39
- 2026-11-13: 39
- 2026-11-12: 38
- 2026-11-11: 38
- 2026-11-10: 37

## Common questions

### What is the io.github.CloudCorpRecords/trenddata MCP server?

io.github.CloudCorpRecords/trenddata is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/trenddata. Google Trends data as JSON: interest over time, geo breakdowns and related queries. This page covers its container image (ghcr.io/cloudcorprecords/trenddata).

### Is the io.github.CloudCorpRecords/trenddata MCP server safe to use?

io.github.CloudCorpRecords/trenddata scores 43 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 io.github.CloudCorpRecords/trenddata MCP server expose?

io.github.CloudCorpRecords/trenddata exposes 1 tool: hasdata_google_trends_search_getTrendsData. Their descriptions and schemas cost roughly 837 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/trenddata MCP server still maintained?

io.github.CloudCorpRecords/trenddata 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 io.github.CloudCorpRecords/trenddata MCP server under?

io.github.CloudCorpRecords/trenddata 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 io.github.CloudCorpRecords/trenddata MCP server?

VerifyMCP ran 12 checks on io.github.CloudCorpRecords/trenddata, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/trenddata: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/cloudcorprecords/trenddata
- Repository: https://github.com/CloudCorpRecords/trenddata
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-trenddata/ghcr-io-cloudcorprecords-trenddata.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-trenddata/ghcr-io-cloudcorprecords-trenddata/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-trenddata/ghcr-io-cloudcorprecords-trenddata.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-trenddata/ghcr-io-cloudcorprecords-trenddata
