Other · Remote MCP server
Google Trends API: Bulk Trend Summaries
Bulk Google Trends: interest over time, regions, rising queries and plain-English trend summaries.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.meridianlabssoftware/google-trends- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-26
- Updated
- 2026-09-26
- Publisher
- com.meridianlabssoftware · 4 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via the domain meridianlabssoftware.com · how
- Website
- apify.com/meridianlabs/google-trends-scraper
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.apify.com/?tools=meridianlabs/google-trends-scraper | Authorization (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; a Bearer token is asked for
- Checked on
- 2026-10-05
How to connect Google Trends API: Bulk Trend Summaries
Google Trends API: Bulk Trend Summaries is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.apify.com/?tools=meridianlabs/google-trends-scraper, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from com.meridianlabssoftware
| Server | Runs |
|---|---|
| Backlink Checker: Referring Domains & Spam ScoreBulk backlink data: domain rank, referring domains, backlinks with anchors, spam score, dofollow. | Remote · HTTPLive check: sign-in required |
| Greenhouse, Lever & Ashby Jobs + SalaryLive jobs from Greenhouse, Lever, Ashby, Workable, Recruitee and Teamtailor, with normalised salary. | Remote · HTTPLive check: sign-in required |
| Keyword Search Volume, CPC & TrendsBulk keyword search volume, CPC, competition and difficulty, plus an optional Google Trends summary. | Remote · HTTPLive check: sign-in required |
More other servers
| Server | Runs |
|---|---|
| Google Sheets MCPGoogle Sheets as MCP tools: read ranges, write without destroying formulas, format and validate. | Local · stdio |
| Google Tag Manager MCPMCP server for the Google Tag Manager API v2: containers, workspaces, tags, triggers, publishing. | Local · stdio |
| Google TrendsGoogle Trends: Trending Now, interest over time, regions, related searches. No API key. | Local · stdio |
| Google Trends APIGoogle Trends in bulk: interest over time, by region, related and rising queries, trending now. | Remote · HTTPLive check: sign-in required |
| Google Trends MCPGoogle Trends MCP with proxy rotation, auto-retry on Google blocks, residential-proxy setup. | Local · stdio |
| Google Trends MCPGoogle Trends MCP server: interest over time, comparisons, related queries, trending searches. | Local · stdio |
| Google Trends ProUnlimited keywords on one Google Trends scale, with daily history, trend status and forecasts. | Remote · HTTPLive check: sign-in required |
| Google Workspace MCPGoogle Workspace Admin via MCP. Manage users, groups, aliases, org units. | Local · stdio |