HasData Google Trends MCP Server

What the code does

We read the source, 1 d ago · tools taken from the live server · rules ccca72095570

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    rc = subprocess.call(args)

const child = spawn(process.execPath, [proxy, URL, '--header', `x-api-key:${key}`], { stdio: 'inherit' });

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

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

{
  "mcpServers": {
    "google-trends": {
      "url": "https://mcp.hasdata.com/api/mcp?apis=google_trends"
    }
  }
}

[mcp_servers.google-trends]
url = "https://mcp.hasdata.com/api/mcp?apis=google_trends"

{
  "mcpServers": {
    "google-trends": {
      "url": "https://mcp.hasdata.com/api/mcp?apis=google_trends"
    }
  }
}

{
  "mcpServers": {
    "google-trends": {
      "url": "https://mcp.hasdata.com/api/mcp?apis=google_trends"
    }
  }
}

This one needs environment variables set before it will start: HASDATA_API_KEY (HasData API key, created at app.hasdata.com. 1,000 free credits every month, no card.). The author declared them in the registry entry; get the values from the project itself.

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

Endpoints