io.github.purahmanian/google-trends-mcp
NPM · GOOGLE-TRENDS-MCP
Google Trends MCP server: interest over time, comparisons, related queries, trending searches
Available components
Last scanned (18 hours ago)
Scores higher than 93% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to purahmanian/google-trends-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 151 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 459 tokens (~91/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −1
- Stability: pass → 0.90 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
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 5 Nov 2026 · Analysed npm/google-trends-mcp@0.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | purahmanian/google-trends-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/purahmanian/google-trends-mcp/.github/workflows/release.yml@refs/tags/v0.1.1 |
| Rekor log index | 1740139828 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:8633c4c464a1ace0fa85357ad1c93f3e8af5f40f373905273acaa6561017e0df4f10e772cca34577a89a4670e719ede6878a1f656e02d1b638f1cf473 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
compare_terms ~84
Compare 2-5 search terms against each other using Google Trends normalized interest scores. Returns the time series, averages per term, and identifies which term has the highest overall interest.
| Name | Type | Req | Description |
|---|---|---|---|
| geo | string | – | Two-letter country code or empty for worldwide. |
| terms | array | yes | Search terms to compare (2-5). |
| timeframe | string | – | Trends timeframe string. |
No output schema declared.
No examples provided.
interest_by_region ~103
Get Google Trends interest scores broken down by region (sub-country or country, depending on the geo parameter). Returns top regions with the highest relative interest for the given term.
| Name | Type | Req | Description |
|---|---|---|---|
| geo | string | – | Two-letter country code to drill into sub-regions (e.g. "US" gives US states), or empty for worldwide country-level breakdown. |
| term | string | yes | The search term to get regional interest for. |
| timeframe | string | – | Trends timeframe string. |
No output schema declared.
No examples provided.
interest_over_time ~124
Fetch Google Trends interest scores (0-100) for up to 5 search terms over a time range. Returns a time series with one value per term per data point. Useful for spotting seasonality, growth, or decline in search interest.
| Name | Type | Req | Description |
|---|---|---|---|
| geo | string | – | Two-letter country code (e.g. "US") or empty for worldwide. |
| terms | array | yes | Search terms (1-5). |
| timeframe | string | – | Trends timeframe string, e.g. "today 12-m", "today 5-y", "now 7-d". |
No output schema declared.
No examples provided.
related_queries ~89
Get rising and top related search queries for a given term from Google Trends. Rising queries have seen the largest recent growth; top queries have the most overall volume. Useful for discovering adjacent keywords and content ideas.
| Name | Type | Req | Description |
|---|---|---|---|
| geo | string | – | Two-letter country code or empty for worldwide. |
| term | string | yes | The search term to get related queries for. |
| timeframe | string | – | Trends timeframe string. |
No output schema declared.
No examples provided.
trending_now ~59
Get today's daily trending searches for a country from Google Trends. Returns the top trending queries with estimated traffic and linked news articles.
| Name | Type | Req | Description |
|---|---|---|---|
| geo | string | – | Two-letter country code (e.g. "US", "GB", "IN", "AU"). |
No output schema declared.
No examples provided.
How do I install the io.github.purahmanian/google-trends-mcp server?
io.github.purahmanian/google-trends-mcp runs locally as an npm package, launched with npx -y google-trends-mcp. 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
claude mcp add purahmanian-google-trends-mcp -- npx -y google-trends-mcp
What is the io.github.purahmanian/google-trends-mcp server?
io.github.purahmanian/google-trends-mcp is listed in the public MCP registry as io.github.purahmanian/google-trends-mcp. Google Trends MCP server: interest over time, comparisons, related queries, trending searches. This page covers its npm package (google-trends-mcp).
Is the io.github.purahmanian/google-trends-mcp server safe to use?
io.github.purahmanian/google-trends-mcp scores 90 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.purahmanian/google-trends-mcp server expose?
io.github.purahmanian/google-trends-mcp exposes 5 tools: interest_over_time, compare_terms, related_queries, trending_now, interest_by_region. Their descriptions and schemas cost roughly 459 tokens of context every time the server is loaded.
Is the io.github.purahmanian/google-trends-mcp server still maintained?
io.github.purahmanian/google-trends-mcp is still listed as active in the MCP registry. We last reached this channel on 5 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.purahmanian/google-trends-mcp server under?
io.github.purahmanian/google-trends-mcp 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.purahmanian/google-trends-mcp server?
VerifyMCP ran 16 checks on io.github.purahmanian/google-trends-mcp, 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.