Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Google data (Trends, YouTube, Ads Transparency, Play)

PYPI · GOOGLE-DATA-MCP · SCANNED SEP 20

Google Trends, YouTube, Ads Transparency and Play reviews over plain HTTP. No API key.

Available components

0 this week 84 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 847 tokens (~121/item across 7 items; 7 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 Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the Google data (Trends, YouTube, Ads Transparency, Play) MCP server?

Google data (Trends, YouTube, Ads Transparency, Play) runs locally as a PyPI package, launched with uvx google-data-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · google-data-mcp

# add to Claude Code
claude mcp add ducnhd-google-data-mcp -- uvx google-data-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "ducnhd-google-data-mcp": {
      "command": "uvx",
      "args": [
        "google-data-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ducnhd-google-data-mcp": {
      "command": "uvx",
      "args": [
        "google-data-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add ducnhd-google-data-mcp -- uvx google-data-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ducnhd-google-data-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "google-data-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ducnhd-google-data-mcp --command uvx --arg google-data-mcp
# ~/.hermes/config.yaml
mcp_servers:
  ducnhd-google-data-mcp:
    command: "uvx"
    args: ["google-data-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ducnhd-google-data-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "google-data-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add ducnhd-google-data-mcp -t stdio -c uvx -a google-data-mcp
// mcp.json
{
  "mcpServers": {
    "ducnhd-google-data-mcp": {
      "command": "uvx",
      "args": [
        "google-data-mcp"
      ]
    }
  }
}
Changelog

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.

  • 19 Sept 26 +1

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

  • 17 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 26 +16
    • Malware scan: unverified → pass security
  • 14 Sept 26 −15
    • Malware scan: pass → unverified security
  • 12 Sept 26 +1

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

  • 10 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 9 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 Sept 2026 · Analysed pypi/google-data-mcp@0.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 29 packages
Packages resolved 29
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~778 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
google_ads_advertisers ~69

Find advertisers in Google's Ads Transparency Center by name. Returns each advertiser's id, country and Google's declared ad count — pass the id to google_ads_creatives.

NameTypeReqDescription
keywordstringyesAdvertiser or brand name to search.
limitintegerHow many matches to return.

No output schema declared.

No examples provided.

google_ads_creatives ~88

Every ad an advertiser is currently running, from Google's Ads Transparency Center: creative id, format, preview URL and first/last shown dates. An advertiser with zero ads is a real answer — Google keeps advertisers whose ads have stopped running.

NameTypeReqDescription
advertiserstringyesAn AR… advertiser id, or a Transparency Center URL containing one.
limitintegerMaximum ads to return.

No output schema declared.

No examples provided.

google_play_reviews ~161

Reviews for an Android app: rating, text, date, app version, thumbs-up and the developer's reply. Reviewer names and avatars are omitted unless you ask for them. Note each language/country returns a DIFFERENT set of reviews, so vary hl/gl to widen coverage.

NameTypeReqDescription
app_idstringyesAndroid package name, e.g. com.spotify.music.
glstringCountry code.
hlstringLanguage code. Each language returns a different set of reviews.
include_authorbooleanInclude the reviewer's display name. Off by default: it is personal data and rarely needed for product or ASO analysis.
limitintegerMaximum reviews.
sortstringGoogle's own ordering.

No output schema declared.

No examples provided.

google_trends_compare ~112

Compare up to 5 keywords in ONE Google Trends request, so their 0-100 values ARE normalised against each other and can be ranked. Google silently drops a 6th term, so 6+ is refused rather than answered with a term missing.

NameTypeReqDescription
geostringCountry or sub-region code. Empty = worldwide.
keywordsarrayyes2 to 5 search terms.
timeframestringGoogle range string, e.g. 'today 12-m'.

No output schema declared.

No examples provided.

google_trends_interest ~141

Google Trends interest over time for ONE keyword. Values are 0-100 relative WITHIN this single request, so they are not comparable to another call's numbers — use google_trends_compare when you need to rank terms against each other.

NameTypeReqDescription
geostringCountry or sub-region code (US, VN, US-CA). Empty = worldwide.
keywordstringyesA single search term.
timeframestringGoogle's own range string: 'today 12-m', 'today 5-y', 'now 7-d', 'all', or '2025-01-01 2025-12-31'.

No output schema declared.

No examples provided.

google_trends_trending ~77

What is trending on Google right now in one country. `searchVolume` is Google's own rounded bucket (100000, 1000000), not a precise count.

NameTypeReqDescription
geostringTwo-letter country code, e.g. US, VN, GB.
limitintegerHow many terms to return.

No output schema declared.

No examples provided.

youtube_listing ~130

List videos from YouTube: a channel's Shorts tab, a channel's videos tab, or search results. Returns videoId, title, view count, and (for videos/search) a publish date. Transcripts are NOT available from this server — Google gates them behind a token this server cannot mint.

NameTypeReqDescription
kindstringWhich listing to read.
limitintegerMaximum rows. Pagination stops early if the listing runs out.
targetstringyesA channel (@handle, UC… id or URL) for 'shorts'/'videos'; a search query for 'search'.

No output schema declared.

No examples provided.

Common questions

What is the Google data (Trends, YouTube, Ads Transparency, Play) MCP server?

Google data (Trends, YouTube, Ads Transparency, Play) is an MCP server listed in the public MCP registry as io.github.ducnhd/google-data-mcp. Google Trends, YouTube, Ads Transparency and Play reviews over plain HTTP. No API key. This page covers its PyPI package (google-data-mcp).

Is the Google data (Trends, YouTube, Ads Transparency, Play) MCP server safe to use?

Google data (Trends, YouTube, Ads Transparency, Play) scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 data (Trends, YouTube, Ads Transparency, Play) MCP server expose?

Google data (Trends, YouTube, Ads Transparency, Play) exposes 7 tools: google_trends_interest, google_trends_compare, google_trends_trending, youtube_listing, google_ads_advertisers, and 2 more. Their descriptions and schemas cost roughly 778 tokens of context every time the server is loaded.

Is the Google data (Trends, YouTube, Ads Transparency, Play) MCP server still maintained?

Google data (Trends, YouTube, Ads Transparency, Play) is still listed as active in the MCP registry. We last reached this channel on 20 September 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 data (Trends, YouTube, Ads Transparency, Play) MCP server under?

Google data (Trends, YouTube, Ads Transparency, Play) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.