Other · Remote MCP server
Google Trends Pro
Unlimited keywords on one Google Trends scale, with daily history, trend status and forecasts.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.mufmo130/google-trends-pro- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-24
- Updated
- 2026-09-24
- Publisher
- mufmo130 (GitHub) · 4 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/mufmo130) · how
- Listed under
- Weather MCP servers
- Website
- apify.com/lsso/google-trends-scraper-pro
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.apify.com?tools=lsso/google-trends-scraper-pro | 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 Pro
Google Trends Pro is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.apify.com?tools=lsso/google-trends-scraper-pro, 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 mufmo130 (GitHub)
| Server | Runs |
|---|---|
| AI Search Visibility TrackerHow often ChatGPT, Perplexity, Gemini and Claude mention and cite your brand vs competitors. | Remote · HTTPLive check: sign-in required |
| App Review InsightsAnalyze App Store and Google Play reviews: themes that cost stars, regressions, feature requests. | Remote · HTTPLive check: sign-in required |
| YouTube Transcript ExtractorTranscripts of YouTube videos, playlists and channels in any language: text, SRT, VTT or JSON. | Remote · HTTPLive check: sign-in required |
More other servers
| Server | Runs |
|---|---|
| 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 API: Bulk Trend SummariesBulk Google Trends: interest over time, regions, rising queries and plain-English trend summaries. | 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 Workspace MCPGoogle Workspace Admin via MCP. Manage users, groups, aliases, org units. | Local · stdio |
| Google_docsGoogle Docs MCP Pack - read, create, and edit Google Docs via OAuth. | Remote · HTTPLive check: ✓ handshake |
| GooglebotValidate whether an IP address belongs to Googlebot. Remote MCP server exposing a validate_ip tool. | Remote · HTTPLive check: ✓ handshake |
| GopeakGoPeak - The most comprehensive MCP server for Godot Engine. 95+ tools, LSP, DAP, screenshots. | Local · stdio |