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.den-indance/google-trends-mcp

NPM · @DEN.DANCE/GOOGLE-TRENDS-MCP · SCANNED AUG 3

Google Trends MCP with proxy rotation, auto-retry on Google blocks, residential-proxy setup.

+19 this week 62 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 (100 of 104), 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 (100 of 104), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability49
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 218 tokens (~43/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 Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 33% of tool parameters carry a description.Partial
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 · @den.dance/google-trends-mcp

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

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

  • 2 Aug 26 +27
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • License: unverified → pass functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Stability: unverified → 0.23 functional
    • Schema quality: unverified → fair functional
    • Dependency health: unverified → partial functional
    • Licence: MIT functional
  • 1 Aug 26 +29
    • Malware scan: unverified → pass security
    • Tool coverage: unverified → 100 functional
  • 31 Jul 26 −38
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 43

    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/@den.dance/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 100 packages

100 packages in the resolved dependency tree · 99 deprecated · 31 stale.

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

MCP tools — 5 exposed · ~218 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_keywords ~70

Compare search interest over time for up to 5 keywords

NameTypeReqDescription
geostringCountry code e.g. US, RU (default: worldwide)
keywordsarrayyesUp to 5 keywords
timeframestringe.g. today 12-m, today 5-y

No output schema declared.

No examples provided.

get_interest_by_region ~42

Get search interest by region/country for a keyword

NameTypeReqDescription
geostring
keywordstringyes
timeframestring

No output schema declared.

No examples provided.

get_related_queries ~40

Get top and rising related queries for a keyword

NameTypeReqDescription
geostring
keywordstringyes
timeframestring

No output schema declared.

No examples provided.

proxy_refresh ~40

Re-validate the current proxy source (PROXY_LIST or PROXY_LIST_FILE). Blocks until done. No-op for PROXY_URL single-proxy mode.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

proxy_status ~26

Show proxy pool status: source, working count, age, freshness, and validation progress

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.