Google Ads Transparency MCP: Competitor Ads
PYPI · GOOGLE-ADS-TRANSPARENCY-MCP-SERVER · 2 COMPONENTS
Competitor Google ads from the Ads Transparency Center: new, running and stopped, with shown dates.
Available components
Last scanned (2 hours ago)
Scores higher than 76% of PyPI servers
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to GeminiGeorge22/google-ads-transparency-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability52
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 540 tokens (~540/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/google-ads-transparency-mcp-server@0.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | GeminiGeorge22/google-ads-transparency-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/GeminiGeorge22/google-ads-transparency-mcp/.github/workflows/pypi-publish.yml@refs/tags/python-v0.1.0 |
| Rekor log index | 3680828656 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:dd3260bd107608910e71d94d26ae30ba8e19c0e4a8f5a3aaafe6b09dbbdcf5c3 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
publicrecords--google-ads-transparency-scraper Google Ads Transparency Scraper: Competitor Ads ~496
Google Ads Transparency Scraper: Competitor Ads. Track competitors' Google ads by website or advertiser ID: new, running and stopped ads with first and last shown dates, days shown and ad links. No login, no proxy. When to use: Use when you need the Google ads a competitor runs (by website domain, Google advertiser ID, Ads Transparency Center link or advertiser name): which ads are new, still running or stopped in a look-back window, with first and last shown dates, days shown and ad links, optionally for one country. Good for weekly competitor ad monitoring; not for ad spend, clicks or keyword bids. Returns: the run's dataset rows as structured JSON (one row per result), plus the run and dataset IDs for paging the full dataset. Behavior: starts one run of the Apify Actor "publicrecords/google-ads-transparency-scraper" through Apify's hosted MCP gateway (mcp.apify.com) with your own APIFY_TOKEN; the run uses your Apify account. Read-only: it only reads public web data and changes nothing on the source site. Docs: https://apify.com/publicrecords/google-ads-transparency-scraper
| Name | Type | Req | Description |
|---|---|---|---|
| includeRegionStats | boolean | – | Adds the countries each ad ran in and, for EU countries, Google's impression ranges. Slower: one extra request per ad. |
| maxAdsPerTarget | integer | – | 0 means no limit. A website search returns every ad that links to it, which for big marketplaces is millions; use an advertiser ID for one company's own ads. |
| region | string | – | Only ads shown in this country. "Anywhere" returns ads from every country. |
| sinceDays | integer | – | Ads first shown in this window are "new"; ads that stopped inside it are "stopped". Google lists an ad 2–3 days after it runs, so on a schedule use your interval plus 3 days (10 for weekly) and match… |
| statuses | array | – | Leave all selected for every ad Google still lists (about one year back). Select only new, running and stopped for a faster weekly monitor. |
| targets | array | yes | One per line: a website domain (nike.com), a Google advertiser ID (AR…), an Ads Transparency Center link, or an exact advertiser name. Example: ["nike.com"] |
No output schema declared.
No examples provided.
How do I install the Google Ads Transparency MCP: Competitor Ads server?
Google Ads Transparency MCP: Competitor Ads runs locally as a PyPI package, launched with uvx google-ads-transparency-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · google-ads-transparency-mcp-server
claude mcp add geminigeorge22-google-ads-transparency-mcp -- uvx google-ads-transparency-mcp-server
What is the Google Ads Transparency MCP: Competitor Ads server?
Google Ads Transparency MCP: Competitor Ads is listed in the public MCP registry as io.github.GeminiGeorge22/google-ads-transparency-mcp. Competitor Google ads from the Ads Transparency Center: new, running and stopped, with shown dates. This page covers its PyPI package (google-ads-transparency-mcp-server).
Is the Google Ads Transparency MCP: Competitor Ads server safe to use?
Google Ads Transparency MCP: Competitor Ads scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Google Ads Transparency MCP: Competitor Ads server expose?
Google Ads Transparency MCP: Competitor Ads exposes 1 tool: publicrecords--google-ads-transparency-scraper. Their descriptions and schemas cost roughly 496 tokens of context every time the server is loaded.
Is the Google Ads Transparency MCP: Competitor Ads server still maintained?
Google Ads Transparency MCP: Competitor Ads is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Google Ads Transparency MCP: Competitor Ads server under?
Google Ads Transparency MCP: Competitor Ads declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.