Data · Remote MCP server
Google Ads Transparency Center Scraper (orbots) - Apify Actor
Every ad an advertiser runs on Google, from the public Ads Transparency Center. Unofficial tool.
Visit Google Ads Transparency Center 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-ads-transparency-scraper- Version
- 0.1.2
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP
- Published
- 2026-09-06
- Updated
- 2026-09-06
- 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-ads-transparency-scraper
- Repository
- github.com/orbotshq/google-ads-transparency-scraper
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.apify.com/?tools=orbots/google-ads-transparency-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 Ads Transparency Center Scraper (orbots) - Apify Actor
Google Ads Transparency Center Scraper (orbots) - Apify Actor is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.apify.com/?tools=orbots/google-ads-transparency-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 Trends Scraper (orbots) - Apify ActorGoogle Trends trending searches, volume estimates & trend duration. Not affiliated with Google LLC. | Remote · HTTPLive check: sign-in required |
More data servers
| Server | Runs |
|---|---|
| Google Ads + Meta Ads + SEO/GEO MCPGoogle Ads, Meta Ads, SEO, GEO & GA4 MCP by Ryze AI - audits, reports, keywords, Search Console. | Remote · HTTPLive check: sign-in required |
| Google Ads Intent MCPDry-run-first Google Ads search-term intent analyzer and negative-keyword MCP for agents. | Local · stdio |
| Google Ads TransparencyQuery Google Ads Transparency data: advertiser suggestions, creatives, and ad history. | Remote · HTTPLive check: ✓ handshake |
| Google Ads Transparency Center ScraperGoogle Ads by domain or brand: creatives, formats, dates; or bulk-check which domains advertise. | Remote · HTTPLive check: sign-in required |
| Google AI Overview Tracker (via Apify)Check if Google AI Overviews cite your website: citations, competitors and changes over time. | Remote · HTTPLive check: sign-in required |
| Google AnalyticsQuery GA4 analytics data with custom reports, pivot tables, and audience exports. | Local · stdio |
| Google Analytics (unofficial)Connect Google Analytics to ChatGPT. Query GA4 data in plain English and get instant insights. | Remote · HTTPLive check: ✓ handshake |
| Google Analytics 4Google Analytics 4 MCP server with reporting, schema discovery, and admin visibility tools. | Local · stdio |