Data · Remote MCP server
Google Trends Scraper (orbots) - Apify Actor
Google Trends trending searches, volume estimates & trend duration. Not affiliated with Google LLC.
Visit Google Trends Scraper (orbots) - Apify Actor's website
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.orbotshq/google-trends-scraper- Version
- 0.1.20
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP
- Published
- 2026-08-26
- Updated
- 2026-08-26
- Publisher
- orbotshq (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/orbotshq) · how
- Listed under
- Apify MCP servers
- Website
- apify.com/orbots/google-trends-scraper
- Repository
- github.com/orbotshq/google-trends-scraper
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.apify.com/?tools=orbots/google-trends-scraper | Authorization (required, 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 Scraper (orbots) - Apify Actor
Google Trends Scraper (orbots) - Apify Actor is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.apify.com/?tools=orbots/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 (required, 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 orbotshq (GitHub)
| Server | Runs |
|---|---|
| Google Ads Transparency Center Scraper (orbots) - Apify ActorEvery ad an advertiser runs on Google, from the public Ads Transparency Center. Unofficial tool. | Remote · HTTPLive check: sign-in required |
More data servers
| Server | Runs |
|---|---|
| Google Search data for agents1 Google Search endpoints. Pay per call in USDC via x402. | Remote · HTTPLive check: ✓ handshake |
| Google Surf MCPWeb, academic and code search with graph RAG, data lineage, ontology and cross-project schema links. | Local · stdio |
| Google Trends (via Apify)Google Trends data for AI agents: interest over time, regions, rising queries and trending searches. | Remote · HTTPLive check: sign-in required |
| Google Trends APIGoogle Trends search interest over time with growth metrics. Free key at trendsapi.ai. | Remote · HTTPLive check: ✓ handshake |
| Google Web SearchGoogle Web Search: Google Web Search API. Search the world’s information, including webpages. | Remote · HTTPLive check: ✓ handshake |
| Googlesearch ApiGoogleSearch API: Fetch real-time Google Search results including title, links Ideal for serp api. | Remote · HTTPLive check: ✓ handshake |
| Goro62 real-world tools for agents: search, scraping, social, enrichment, image, video, voice. | Remote · HTTPLive check: sign-in required |
| Gov AuctionsGovernment Auctions MCP - physical-asset auctions (surplus, seized, forfeited,. | Remote · HTTPLive check: ✓ handshake |