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

io.github.purahmanian/google-trends-mcp

NPM · GOOGLE-TRENDS-MCP · SCANNED AUG 3

Google Trends MCP server: interest over time, comparisons, related queries, trending searches

Available components

+33 this week 79 Trust /100
Trust breakdown (6 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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. 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 57 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
  • 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 Management23
  • Stability observed for 7 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · google-trends-mcp

# add to Claude Code
claude mcp add purahmanian-google-trends-mcp -- npx -y google-trends-mcp
# add to Codex CLI
codex mcp add purahmanian-google-trends-mcp -- npx -y google-trends-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "purahmanian-google-trends-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "google-trends-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add purahmanian-google-trends-mcp --command npx --arg -y --arg google-trends-mcp
# ~/.hermes/config.yaml
mcp_servers:
  purahmanian-google-trends-mcp:
    command: "npx"
    args: ["-y", "google-trends-mcp"]
// mcp.json
{
  "mcpServers": {
    "purahmanian-google-trends-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "google-trends-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.

  • 3 Aug 26 +3
    • Stability: unverified → 0.23 functional
  • 2 Aug 26 +55
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Provenance: unverified → pass security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • The attested source repository moved: purahmanian/google-trends-mcp security
    • Security disclosure: fail → unverified functional
    • Tool coverage: 100 → unverified functional
    • Schema quality: unverified → excellent functional
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • First check of Schema quality: unverified functional
    • Licence: MIT functional
  • 1 Aug 26 −7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 46

    First indexed and scored.

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

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:
https://slsa.dev/provenance/v1
Subject digest:
sha512:8633c4c464a1ace0fa85357ad1c93f3e8af5f40f373905273acaa6561017e0df4f10e772cca34577a89a4670e719ede6878a1f656e02d1b638f1cf473
Discovery method:
attestation_endpoint
Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 5 exposed · ~459 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.

Tool Tokens
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.

NameTypeReqDescription
geostringTwo-letter country code or empty for worldwide.
termsarrayyesSearch terms to compare (2-5).
timeframestringTrends 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.

NameTypeReqDescription
geostringTwo-letter country code to drill into sub-regions (e.g. "US" gives US states), or empty for worldwide country-level breakdown.
termstringyesThe search term to get regional interest for.
timeframestringTrends 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.

NameTypeReqDescription
geostringTwo-letter country code (e.g. "US") or empty for worldwide.
termsarrayyesSearch terms (1-5).
timeframestringTrends 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.

NameTypeReqDescription
geostringTwo-letter country code or empty for worldwide.
termstringyesThe search term to get related queries for.
timeframestringTrends 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.

NameTypeReqDescription
geostringTwo-letter country code (e.g. "US", "GB", "IN", "AU").

No output schema declared.

No examples provided.