Google Ads Transparency Monitor MCP server
List the Google ads a company runs, from the Ads Transparency Center, with a company summary.
0 stars103 downloads/wk
Reviews
Write oneNobody has reviewed Google Ads Transparency Monitor yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Google Ads Transparency Monitor tools (1)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
get_google_adsList the Google ads a company runs, read from Google's public Ads Transparency Center. Give a company domain (for example stripe.com) or an advertiser name, or lists of either. Returns one row per ad with the advertiser, ad ID, format (text, image, or video), first and last shown dates, a creative link, and the ad's Transparency Center page, plus one company summary row per input with Google's tot
Public scan report
scanner v0.1.10 · 2026-10-27 · same rubric, same numbers if you re-run it
- Code scan2 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 7 days ago15/15
- Maintainer identitynamespace and repository owner differ4/10
How Google Ads Transparency Monitor compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,273 servers
- Tools
- 1
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 103
- more than 64% of 11,915 servers with a package
What its tools let an agent do: 1 read
Install Google Ads Transparency Monitor in Claude Code, Cursor or VS Code
Runs npx -y @mambalabsdev/mcp-google-ads-transparency-monitor on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add mcp-google-ads-transparency-monitor -- npx -y @mambalabsdev/mcp-google-ads-transparency-monitor
What the publisher says
From the Google Ads Transparency Monitor repository's README, as published. We do not edit it. Read it on GitHub
Google Ads Transparency Monitor MCP Server
An MCP server for the Mamba Labs Google Ads Transparency Monitor actor on Apify. Give it a company domain or an advertiser name. Each run reads Google's public Ads Transparency Center and returns one row per ad, with the format, first and last shown dates, a creative link, and the ad's page, plus a company summary row with Google's total ad count band.
What's Inside
- What it does
- Quick start
- Prerequisites
- Example prompts
- Tool
- Inputs
- Pricing
- Your keys
- Full actor documentation
- License
What it does
List the Google ads a company runs. Give a company domain (for example stripe.com) or an advertiser name, or lists of either. You get one row per ad with the advertiser, ad ID, format (text, image, or video), first and last shown dates, a creative link, and the ad's Transparency Center page, plus one summary row per input that says whether the company runs Google ads, how many (Google's own count band, for example 8,000 to 9,000), and in which formats. Rows with no ads, blocked requests, or a changed Google page come back free with a row_status saying so.
All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.
Quick start
You need Node.js 18 or newer and an Apify account with an API token.
Add this to your Claude Desktop config (claudedesktopconfig.json), Cursor, or any MCP client:
{
"mcpServers": {
"mamba-google-ads-transparency-monitor": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-google-ads-transparency-monitor"
],
"env": {
"APIFY_TOKEN": "your-apify-token"
}
}
}
}Restart the client. The getgoogleads tool appears.
Prerequisites
- Node.js 18 or newer.
- An Apify API token from console.apify.com/account/integrations, set as APIFY_TOKEN. The server lists its tool without a token; a call needs one.
Example prompts
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Google Ads Transparency Monitor: common questions
- Is Google Ads Transparency Monitor MCP server safe?
- Mostly: it is graded B (77/100). Read the Google Ads Transparency Monitor safety report
- How do I install Google Ads Transparency Monitor?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Google Ads Transparency Monitor need an API key?
- Yes. The registry entry asks for
APIFY_TOKEN. - Is Google Ads Transparency Monitor maintained?
- The last commit was 13 days ago (2026-10-20). The latest release is v1.0.1.
- What can I use instead of Google Ads Transparency Monitor?
- Servers from other publishers that do the same job: AdLoop MCP server.
- How does Google Ads Transparency Monitor compare with other MCP servers?
- safety score 77/100 (higher than 50% of 48,273 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Google Ads Transparency Monitor
Same job from other publishers: the closest match first, then the best rated.
- AdLoopGoogle Ads, Reddit Ads, GA4 and Tag Manager in your AI client, with a preview before every change.not reviewedEstablishedA