Google Trends MCP server
Google Trends MCP with proxy rotation, auto-retry on Google blocks, residential-proxy setup.
1 stars40 downloads/wk
Reviews
Write oneNobody has reviewed Google Trends yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Google Trends tools (5)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
compare_keywordsCompare search interest over time for up to 5 keywords
get_interest_by_regionGet search interest by region/country for a keyword
get_related_queriesGet top and rising related queries for a keyword
proxy_refreshRe-validate the current proxy source (PROXY_LIST or PROXY_LIST_FILE). Blocks until done. No-op for PROXY_URL single-proxy mode.
proxy_statusShow proxy pool status: source, working count, age, freshness, and validation progress
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan4 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 128 days ago8/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Google Trends compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 72/100
- higher than 38% of 48,273 servers
- Tools
- 5
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 1
- more than 65% of 28,534 servers
- Downloads a week
- 40
- more than 33% of 11,915 servers with a package
What its tools let an agent do: 5 read
Install Google Trends in Claude Code, Cursor or VS Code
Runs npx -y @den.dance/google-trends-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add google-trends-mcp -- npx -y @den.dance/google-trends-mcp
What the publisher says
From the Google Trends repository's README, as published. We do not edit it. Read it on GitHub
Google Trends MCP
The Google Trends MCP server that actually works under Google's anti-bot. Connect Claude to live Google Trends data — keyword interest, related queries, regional popularity.
Most Google Trends MCP packages crash with Unexpected token 'l' the moment Google blocks them (which is often). Free public proxy lists don't help — we tested 64 proxies from a popular "high-quality" list and 0 worked. This one uses your own rotating proxy with auto-retry, so blocked requests transparently retry on a fresh IP.
Built by Denys Malieiev.
Why this one
Quick Start
npx @den.dance/google-trends-mcpWorks out-of-the-box from non-flagged IPs, but Google rate-limits datacenter ranges aggressively. For reliable use, set up a proxy (see below).
Setup
1. Get a rotating proxy account
Recommended (all have free tiers / pay-per-GB):
- Webshare — free 1 GB residential (~46k Google Trends requests)
- IPRoyal — $1.75/GB, lowest price
- Smartproxy / Decodo — $4-7/GB, large pool
- Bright Data / Oxylabs — $5-8/GB, enterprise grade
Make sure the provider allows *.google.com in their ToS (most majors do).
2. Configure Claude Desktop
Edit your Claude Desktop config file:
- macOS: ~/Library/Application Support/Claude/claudedesktopconfig.json
- Windows: %APPDATA%\Claude\claudedesktopconfig.json
- Linux: ~/.config/Claude/claudedesktopconfig.json
Single rotating endpoint (recommended — provider rotates IPs internally):
{
"mcpServers": {
"google-trends": {
"command": "npx",
"args": ["@den.dance/google-trends-mcp"],
"env": {
"PROXY_URL": "http://USER:PASS@gate.smartproxy.com:7000"
}
}
}
}Or an explicit list (useful for Webshare-style per-port proxies):
{
"mcpServers": {
"google-trends": {
"command": "npx",
"args": ["@den.dance/google-trends-mcp"],
"env": {
"PROXY_LIST": "http://user:pass@host1:6114,http://user:pass@host2:6014,http://user:pass@host3:5863"
}
}
}
}For longer lists, put proxies in a file (one per line, # comments allowed) and point to it:
{
"mcpServers": {
"google-trends": {
"command": "npx",
"args": ["@den.dance/google-trends-mcp"],
"env": {
"PROXY_LIST_FILE": "/home/you/.config/google-trends/proxies.txt"
}
}
}
}# ~/.config/google-trends/proxies.txt
http://user:pass@host1:6114
http://user:pass@host2:6014
http://user:pass@host3:5863Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Google Trends: common questions
- Is Google Trends MCP server safe?
- Mostly: it is graded B (72/100). Read the Google Trends safety report
- How do I install Google Trends?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Google Trends need an API key?
- Yes. The registry entry asks for
PROXY_URL,PROXY_LIST. - Is Google Trends maintained?
- The last commit was 164 days ago (2026-05-22). The latest release is v1.0.0.
- How does Google Trends compare with other MCP servers?
- safety score 72/100 (higher than 38% of 48,273 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.