com.mambabuilt/mcp-google-ads-transparency-monitor
NPM · @MAMBALABSDEV/MCP-GOOGLE-ADS-TRANSPARENCY-MONITOR
List the Google ads a company runs, from the Ads Transparency Center, with a company summary.
Available components
Last scanned (18 hours ago)
Scores higher than 53% of npm 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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 15 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 524 tokens (~524/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 Management53
- Stability observed for 16 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 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
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 4 Nov 2026 · Analysed npm/@mambalabsdev/mcp-google-ads-transparency-monitor@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
get_google_ads Get Google ads ~524
List 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 total ad count band, formats seen, and whether the company runs Google ads at all. Rows with no ads, blocked requests, or a changed Google page come back free with a row_status saying so. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN and consumes Apify credits per ad row returned.
| Name | Type | Req | Description |
|---|---|---|---|
| advertiser_name | string | – | An advertiser name as Google verifies it, for example Stripe, Inc. Exact name matches are used, up to 5 advertisers; otherwise the closest suggestion, labeled closest. |
| advertiser_names | array | – | Several advertiser names. |
| company_domain | string | – | A company website domain, for example stripe.com. Returns the ads Google lists for that domain. Give this, advertiser_name, or one of the lists. |
| domains | array | – | Several company domains. Each gets its own ad rows and summary row. Up to 500 inputs per run. |
| formats | array | – | Limit to text, image, or video ads. Omit for all formats. |
| include_summary | string | – | One extra summary row per input, billed only when ads were found. Default true. |
| max_ads | string | – | Ad rows per input, 1 to 1000. Each ad row is billed. Default 50. |
| max_charge_usd | string | – | Optional. The run stops before any row that would take its charges over this amount. |
| proxy_mode | string | – | auto connects directly and moves to the Apify proxy default pool if Google refuses a request; direct never uses a proxy; residential uses Apify residential proxy. Proxy use adds nothing to the price.… |
| region | string | – | Where the ads were shown: anywhere, or a two letter country code such as US, GB, DE, or FR. Default anywhere. |
| since_days | string | – | Only ads last shown in this many days. 0 returns every ad Google lists. Default 90. |
| skipCache | string | – | true reads fresh results instead of the free 24 hour cache in your account. Default false. |
No output schema declared.
No examples provided.
How do I install the com.mambabuilt/mcp-google-ads-transparency-monitor server?
com.mambabuilt/mcp-google-ads-transparency-monitor runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-google-ads-transparency-monitor. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mambalabsdev/mcp-google-ads-transparency-monitor
claude mcp add com-mambabuilt-mcp-google-ads-transparency-monit -- npx -y @mambalabsdev/mcp-google-ads-transparency-monitor
What is the com.mambabuilt/mcp-google-ads-transparency-monitor server?
com.mambabuilt/mcp-google-ads-transparency-monitor is listed in the public MCP registry as com.mambabuilt/mcp-google-ads-transparency-monitor. List the Google ads a company runs, from the Ads Transparency Center, with a company summary. This page covers its npm package (@mambalabsdev/mcp-google-ads-transparency-monitor).
Is the com.mambabuilt/mcp-google-ads-transparency-monitor server safe to use?
com.mambabuilt/mcp-google-ads-transparency-monitor scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. 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 com.mambabuilt/mcp-google-ads-transparency-monitor server expose?
com.mambabuilt/mcp-google-ads-transparency-monitor exposes 1 tool: get_google_ads. Their descriptions and schemas cost roughly 524 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-google-ads-transparency-monitor server still maintained?
com.mambabuilt/mcp-google-ads-transparency-monitor is still listed as active in the MCP registry. We last reached this channel on 4 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 com.mambabuilt/mcp-google-ads-transparency-monitor server under?
com.mambabuilt/mcp-google-ads-transparency-monitor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.