mcpbeat Sign in

Google Trends Realtime MCP Server

answering

Google Trends Realtime MCP is answering right now. Last checked 3 min ago.

Google Trends realtime & entities

Uptime history 4 days of history
4 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
383 ms
Response time
average over 24h
authentication required
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Google Trends Realtime MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add google-trends-realtime-mcp --transport http https://mutualistic-housing--google-trends-realtime-mcp.apify.actor/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mutualistic-housing--google-trends-realtime-mcp.apify.actor/mcp
~/.codex/config.toml
[mcp_servers.google-trends-realtime-mcp]
url = "https://mutualistic-housing--google-trends-realtime-mcp.apify.actor/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "google-trends-realtime-mcp": {
      "url": "https://mutualistic-housing--google-trends-realtime-mcp.apify.actor/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "google-trends-realtime-mcp": {
      "type": "http",
      "url": "https://mutualistic-housing--google-trends-realtime-mcp.apify.actor/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://mutualistic-housing--google-trends-realtime-mcp.apify.actor/mcp streamable-http needs auth 373 ms 3 min ago

Alternatives to Google Trends Realtime MCP

same job, measured the same way
Google Trends
by pipeworx-io

MCP server for google-trends

439 installs/wk 45 tools answering
Google Trends MCP
by purahmanian

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

128 installs/wk local only
Google Ads Transparency MCP
by dancerdan15

Google Ads Transparency & ad spy

answering
Google_ads
by pipeworx-io

Google Ads MCP Pack

406 installs/wk 49 tools answering
Korean News Hub
by songt-50

Korean news aggregator - Naver, Google News, Daum trends in real-time

6 tools answering
Google Books
by pipeworx-io

Google Books MCP

411 installs/wk 48 tools answering
Google Analytics
by codechap

MCP server for Google Analytics 4 — reports, realtime data, and admin

local only
Ga4
by mharnett

Google Analytics 4 MCP: reports, realtime data, custom dimensions, data streams.

165 installs/wk local only

Google Trends Realtime MCP — questions

Answers built from our own checks of this server.

Why is there no tool list for Google Trends Realtime MCP?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Google Trends Realtime MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 383 ms. The bar chart above shows every period we have measured.
How do I connect Google Trends Realtime MCP?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does Google Trends Realtime MCP need an API key?
Yes. Every time we knock, Google Trends Realtime MCP answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Google Trends Realtime MCP?
It answers our handshake in 383 ms on average, which is faster than 34% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.