MCP.Market

HasData Google Trends MCP server

online · 100% uptime
by hasdata.com·com.hasdata/google-trends·v1.0.7·5 stars
No reviews yet

Google Trends interest over time, by region, and related queries and topics, as JSON.

A93/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A93/100

full report

Adoption
Growing

5 stars119 downloads/wk

Reviews

Write one

Nobody has reviewed HasData Google Trends yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

HasData Google Trends tools (1)

write = sends, deletes, buys or posts
  • hasdata_google_trends_search_getTrendsDataFree

    Get Google Trends Data Pulls Google Trends data for one or more queries with geo targeting, region granularity (country/subregion/metro/city), date range, category, time zone, Google property (web, images, news, shopping, YouTube), and dataType (timeseries, geoMap, relatedTopics, relatedQueries). Returns interest-over-time series, geo-level breakdowns, and rising/top related topics/queries with relative scores. Use for keyword/content strategy, demand forecasting, seasonality analysis, topic discovery, campaign timing, and adding live-trend signals to marketing or research agents.

Public scan report

scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it

no findings
  • Code scan2 source files scanned; 9 source files scanned25/25
  • Live reliabilityremote reachable in 211ms20/20
  • Tool poisoning1 tool descriptions checked15/15
  • Auth qualityAPI key sent as a header8/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year; website matches verified namespace10/10
Overall 93/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How HasData Google Trends compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
93/100
higher than 96% of 48,255 servers
Tools
1
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
158 ms
faster than 71% of 30,031 servers
GitHub stars
5
more than 83% of 28,688 servers
Downloads a week
119
more than 66% of 12,191 servers with a package

What its tools let an agent do: 1 read

Release history: 3 versions in the registry since 2026-09-09, latest 2026-09-24, typically one every 13 days.

Install HasData Google Trends in Claude Code, Cursor or VS Code

claude mcp add --transport http google-trends https://mcp.hasdata.com/mcp?apis=google_trends
Add to Cursor

What the publisher says

From the HasData Google Trends repository's README, as published. We do not edit it. Read it on GitHub

Google Trends MCP Server

<!-- mcp-name: com.hasdata/google-trends -->

A hosted Model Context Protocol (MCP) server that gives Claude, Cursor, Windsurf and any other MCP client one Google Trends tool. Pull interest over time, interest by region, and the rising and top related queries and topics for any term, all as structured JSON, with no scraping library to keep alive and no Google account.

1,000 free credits every month, no card required, which is 200 Google Trends calls.

https://mcp.hasdata.com/api/mcp?apis=google_trends

Contents

  • What you need
  • Quick start
  • Example prompts
  • Tools
  • Errors and failure paths
  • Pricing, free tier and limits
  • Tool selection
  • How it compares
  • FAQ
  • HasData links
  • Development
  • Contributing

What you need

An MCP client and a HasData API key from the dashboard, free to create with no card, and the free tier covers about 200 calls a month at the 5-credit rate. This is a remote server, so the simplest path is a URL and an x-api-key header, with no container to run and no Google account anywhere in the flow. A client that only speaks stdio reaches it through a thin launcher, published as @hasdata/google-trends-mcp on npm and hasdata-google-trends-mcp on PyPI, shown below.

Quick start

The server URL is the same for every client. We run it hands-on in Claude Code and Claude Desktop. The other blocks follow each client's own documented format for a remote server.

Clients with OAuth support can add the same URL as a connector and sign in without putting a key in a config file.

Claude Code

claude mcp add --transport http google-trends "https://mcp.hasdata.com/api/mcp?apis=google_trends" \
  --header "x-api-key: HASDATA_API_KEY"

Claude Desktop

Settings, then Connectors, then Add custom connector, then paste https://mcp.hasdata.com/api/mcp?apis=google_trends and sign in.

For the config-file route, Claude Desktop loads only local (stdio) servers, so it reaches a remote server through a stdio launcher. The @hasdata/google-trends-mcp package is that launcher, and it reads the key from the environment. Add this to claudedesktopconfig.json:

{
  "mcpServers": {
    "google-trends": {
      "command": "npx",
      "args": ["-y", "@hasdata/google-trends-mcp"],
      "env": { "HASDATA_API_KEY": "YOUR_KEY" }
    }
  }
}

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

HasData Google Trends: common questions

Is HasData Google Trends MCP server safe?
Yes, by our scan: it is graded A (93/100). Read the HasData Google Trends safety report
How do I install HasData Google Trends?
It runs remotely at mcp.hasdata.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does HasData Google Trends need an API key?
Yes. The registry entry asks for HASDATA_API_KEY, x-api-key.
Is HasData Google Trends maintained?
The last commit was 21 days ago (2026-10-14). The latest release is v1.0.7.
Is HasData Google Trends up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does HasData Google Trends compare with other MCP servers?
safety score 93/100 (higher than 96% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from hasdata.com →