# 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.

- Trust score: 76/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- npm · `@mambalabsdev/mcp-google-ads-transparency-monitor`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-mambabuilt-mcp-google-ads-transparency-monitor/mambalabsdev-mcp-google-ads-transparency-monitor.md), [page](https://verifymcp.io/servers/com-mambabuilt-mcp-google-ads-transparency-monitor/mambalabsdev-mcp-google-ads-transparency-monitor)

## Channel facts

- Registry: `npm`
- Package: `@mambalabsdev/mcp-google-ads-transparency-monitor`
- Version: `1.0.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 15 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add com-mambabuilt-mcp-google-ads-transparency-monit -- npx -y @mambalabsdev/mcp-google-ads-transparency-monitor
```

### Cursor

```json
{
  "mcpServers": {
    "com-mambabuilt-mcp-google-ads-transparency-monit": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-google-ads-transparency-monitor"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-mambabuilt-mcp-google-ads-transparency-monit": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-google-ads-transparency-monitor"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-mambabuilt-mcp-google-ads-transparency-monit -- npx -y @mambalabsdev/mcp-google-ads-transparency-monitor
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mambabuilt-mcp-google-ads-transparency-monit": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mambalabsdev/mcp-google-ads-transparency-monitor"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-mambabuilt-mcp-google-ads-transparency-monit --command npx --arg -y --arg @mambalabsdev/mcp-google-ads-transparency-monitor
```

### Hermes

```yaml
mcp_servers:
  com-mambabuilt-mcp-google-ads-transparency-monit:
    command: "npx"
    args: ["-y", "@mambalabsdev/mcp-google-ads-transparency-monitor"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-mambabuilt-mcp-google-ads-transparency-monit": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@mambalabsdev/mcp-google-ads-transparency-monitor"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-mambabuilt-mcp-google-ads-transparency-monit -t stdio -c npx -a -y @mambalabsdev/mcp-google-ads-transparency-monitor
```

### Other

```json
{
  "mcpServers": {
    "com-mambabuilt-mcp-google-ads-transparency-monit": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-google-ads-transparency-monitor"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 76, +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.

### 2026-11-02 (score 75, +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.

### 2026-10-31 (score 74, +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.

### 2026-10-29 (score 73, +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.

### 2026-10-27 (score 72, +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.

### 2026-10-24 (score 71, +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.

### 2026-10-22 (score 70, +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.

### 2026-10-20 (score 69, +11)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.85

## MCP tools (1)

### `get_google_ads` (~524 tokens)

Get Google ads

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.

Input parameters:

- `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.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-mambabuilt-mcp-google-ads-transparency-monitor/mambalabsdev-mcp-google-ads-transparency-monitor#diagnostics

## Score history

- 2026-11-04: 76
- 2026-11-03: 75
- 2026-11-02: 75
- 2026-11-01: 74
- 2026-10-31: 74
- 2026-10-30: 73
- 2026-10-29: 73
- 2026-10-28: 72
- 2026-10-27: 72
- 2026-10-26: 71
- 2026-10-25: 71
- 2026-10-24: 71
- 2026-10-23: 70
- 2026-10-22: 70
- 2026-10-21: 69
- 2026-10-20: 69
- 2026-10-19: 58

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@mambalabsdev/mcp-google-ads-transparency-monitor
- Socket report: https://socket.dev/npm/package/@mambalabsdev/mcp-google-ads-transparency-monitor
- Repository: https://github.com/mambalabsdev/mcp-google-ads-transparency-monitor
- Changelog RSS feed: https://verifymcp.io/servers/com-mambabuilt-mcp-google-ads-transparency-monitor/mambalabsdev-mcp-google-ads-transparency-monitor.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mambabuilt-mcp-google-ads-transparency-monitor/mambalabsdev-mcp-google-ads-transparency-monitor.json
- HTML version of this page: https://verifymcp.io/servers/com-mambabuilt-mcp-google-ads-transparency-monitor/mambalabsdev-mcp-google-ads-transparency-monitor