Google Trends
NPM · GOOGLE-TRENDS-MCP-SERVER
Google Trends interest over time, by region, and trending searches in 125 countries.
Available components
Last scanned (22 hours ago)
Scores higher than 42% of npm servers
Category Search and Retrieval
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 Security89
- No malware found by supply-chain analysis.Pass
- 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. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 47 of 145 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 281 tokens (~140/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +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.
- 19 Nov 26 +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.
- 17 Nov 26 +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.
- 16 Nov 26 +15
- Tool safety: pass → unverified ▼ security
- 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. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 1.0.0 → 1.0.1 functional
- 15 Nov 26 53
First indexed and scored.
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 21 Nov 2026 · Analysed npm/google-trends-mcp-server@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 3 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-5pm8-86m8-9m6r | CVE-2026-126345 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-c475-qrg2-pj4r | CVE-2026-102990 | high | yes | |
| GHSA-r4jh-29pc-gfqr | CVE-2026-126346 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 145 packages
| Packages resolved | 145 |
|---|---|
| Deprecated | 1 |
| Stale | 47 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_interest_over_time Google Trends: interest over time ~164
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | One search term, e.g. "chatgpt" or "electric cars" |
| timeframe | string | – | Period. Short periods give hourly points, long ones daily or weekly |
No output schema declared.
No examples provided.
get_trending_searches Google Trends: trending searches ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
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.
npm · google-trends-mcp-server
claude mcp add dataxplore19-google-trends-mcp-server -- npx -y google-trends-mcp-server
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.