
Google Ads Transparency Center Scraper
io.github.brenton-kellerPublished by GitHub account brenton-kellerv0.1.2Updated Oct 24, 2026
Google Ads by domain or brand: creatives, formats, dates; or bulk-check which domains advertise.
Overview
Queries the Google Ads Transparency Center for ad creatives and domain advertising activity via a remote Apify endpoint.
- What you can do
- Look up Google Ads creatives by domain or brand, with formats and dates. Bulk-check which domains are advertising.
- When to use it
- Use it to inspect the creatives, formats and dates a domain or brand runs on Google Ads, or to bulk-check which domains advertise.
- Requirements
- A connection to the remote MCP endpoint at Apify, plus an Apify account and access token able to run the service; usage may be subject to Apify platform quotas.
Installation
In SourceWeft
- Open Google Ads Transparency Center Scraper in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.brenton-keller%2Fgoogle-ads-transparency-center/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"google-ads-transparency-center-scraper": {
"type": "http",
"url": "https://mcp.apify.com/?tools=brenton8907/google-ads-transparency-center"
}
}
}Tools
0Version history
2- v0.1.2LatestSep 19, 2026
- v0.1.1Sep 16, 2026
Score
28% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.