# com.mambabuilt/mcp-meta-ad-library-monitor (npm · @mambalabsdev/mcp-meta-ad-library-monitor)

Find a company active Facebook and Instagram ads through the Meta Ad Library API.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `@mambalabsdev/mcp-meta-ad-library-monitor`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-mambabuilt-mcp-meta-ad-library-monitor/mambalabsdev-mcp-meta-ad-library-monitor.md), [page](https://verifymcp.io/servers/com-mambabuilt-mcp-meta-ad-library-monitor/mambalabsdev-mcp-meta-ad-library-monitor)

## Channel facts

- Registry: `npm`
- Package: `@mambalabsdev/mcp-meta-ad-library-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-09-20.

- **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.
  - 31 of 96 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 28 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 658 tokens (~658/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**: 90/100
  - Stability observed for 27 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-meta-ad-library-monitor server?

com.mambabuilt/mcp-meta-ad-library-monitor runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-meta-ad-library-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-meta-ad-library-monitor -- npx -y @mambalabsdev/mcp-meta-ad-library-monitor
```

### Cursor

```json
{
  "mcpServers": {
    "com-mambabuilt-mcp-meta-ad-library-monitor": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-meta-ad-library-monitor"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-mambabuilt-mcp-meta-ad-library-monitor": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-meta-ad-library-monitor"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-mambabuilt-mcp-meta-ad-library-monitor -- npx -y @mambalabsdev/mcp-meta-ad-library-monitor
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-mambabuilt-mcp-meta-ad-library-monitor --command npx --arg -y --arg @mambalabsdev/mcp-meta-ad-library-monitor
```

### Hermes

```yaml
mcp_servers:
  com-mambabuilt-mcp-meta-ad-library-monitor:
    command: "npx"
    args: ["-y", "@mambalabsdev/mcp-meta-ad-library-monitor"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-mambabuilt-mcp-meta-ad-library-monitor": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@mambalabsdev/mcp-meta-ad-library-monitor"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-mambabuilt-mcp-meta-ad-library-monitor -t stdio -c npx -a -y @mambalabsdev/mcp-meta-ad-library-monitor
```

### Other

```json
{
  "mcpServers": {
    "com-mambabuilt-mcp-meta-ad-library-monitor": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-meta-ad-library-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-09-19 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-04 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (1)

### `find_meta_ads` (~658 tokens)

Find Meta Ads

Search the Meta Ad Library for a company's ads through Facebook's sanctioned Graph API and return ONE FLAT ROW PER AD with creative text, headline, delivery dates, the Meta surfaces it ran on and Meta's permanent snapshot URL for the rendered ad. COVERAGE IS NOT UNIVERSAL: the Ad Library holds all ads only in the EU and only political and issue ads elsewhere, so a commercial advertiser outside the EU is legitimately absent and every row carries a coverage note saying what the search could have found. Requires the CALLER's own Meta app access token. Impressions and spend exist for political ads only and arrive as bands, so a null there is not zero spend. Read only; requires an APIFY_TOKEN and consumes Apify credits per call.

Input parameters:

- `ad_active_status` (string): Whether to return currently running ads, stopped ads, or both. ACTIVE is the default because a currently running ad is the buying signal; ALL is what you want for a creative history or a competitive…
- `ad_reached_countries` (string): Which country audiences to search. This parameter is REQUIRED by Meta and a request without it fails outright. The EU set is where the Ad Library covers ALL ads rather than only political ones, so it…
- `ad_type` (string): ALL returns every ad the Ad Library holds for those countries. POLITICAL_AND_ISSUE_ADS narrows to the political archive, which is the only archive that carries impressions and spend, and which requir…
- `company_domain` (string): Bare company domain, for example gymshark.com. Used to derive the advertiser search term when no company name is given, and used by the identity gate to check that a matched advertiser page really is…
- `company_name` (string): Strongly recommended here. Meta advertiser search is a fuzzy text search over page names, so the company name is what the identity gate compares a matched page against. Without it the gate falls back…
- `maxAds` (string): How many ad rows to return per company. This is a cost dial, not a change of answer: the row always reports how many ads matched before the cap. Sent as a string for Clay compatibility.
- `media_type` (string): Narrow to a creative format. Useful for a creative teardown where you only care about video, and irrelevant for a simple "are they advertising" check. Sent as a string for Clay compatibility.
- `metaAccessToken` (string): YOUR OWN Meta app access token, free to create at developers.facebook.com. REQUIRED: the Ad Library API is not open. Political and issue ad data additionally requires a verified identity on your Meta…
- `skipCache` (boolean): When "false" (default) a successful lookup is cached for seven days and reused, which costs you nothing on a repeated run. Set "true" to force a fresh fetch. Sent as a string for Clay compatibility.

## Diagnostics

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

## Score history

- 2026-09-20: 80
- 2026-09-19: 80
- 2026-09-18: 79
- 2026-09-17: 79
- 2026-09-16: 79
- 2026-09-15: 78
- 2026-09-14: 78
- 2026-09-13: 77
- 2026-09-12: 77
- 2026-09-11: 76
- 2026-09-10: 76
- 2026-09-09: 75
- 2026-09-08: 75
- 2026-09-07: 74
- 2026-09-06: 74
- 2026-09-05: 73
- 2026-09-04: 73
- 2026-09-03: 72
- 2026-09-02: 72
- 2026-09-01: 72
- 2026-08-31: 68
- 2026-08-30: 68
- 2026-08-29: 68
- 2026-08-28: 68
- 2026-08-27: 68
- 2026-08-26: 68
- 2026-08-25: 66
- 2026-08-24: 66

## Common questions

### What is the com.mambabuilt/mcp-meta-ad-library-monitor server?

com.mambabuilt/mcp-meta-ad-library-monitor is listed in the public MCP registry as com.mambabuilt/mcp-meta-ad-library-monitor. Find a company active Facebook and Instagram ads through the Meta Ad Library API. This page covers its npm package (@mambalabsdev/mcp-meta-ad-library-monitor).

### Is the com.mambabuilt/mcp-meta-ad-library-monitor server safe to use?

com.mambabuilt/mcp-meta-ad-library-monitor scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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-meta-ad-library-monitor server expose?

com.mambabuilt/mcp-meta-ad-library-monitor exposes 1 tool: find_meta_ads. Their descriptions and schemas cost roughly 658 tokens of context every time the server is loaded.

### Is the com.mambabuilt/mcp-meta-ad-library-monitor server still maintained?

com.mambabuilt/mcp-meta-ad-library-monitor is still listed as active in the MCP registry. We last reached this channel on 20 September 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-meta-ad-library-monitor server under?

com.mambabuilt/mcp-meta-ad-library-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-meta-ad-library-monitor
- Socket report: https://socket.dev/npm/package/@mambalabsdev/mcp-meta-ad-library-monitor
- Repository: https://github.com/mambalabsdev/mcp-meta-ad-library-monitor
- Changelog RSS feed: https://verifymcp.io/servers/com-mambabuilt-mcp-meta-ad-library-monitor/mambalabsdev-mcp-meta-ad-library-monitor.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mambabuilt-mcp-meta-ad-library-monitor/mambalabsdev-mcp-meta-ad-library-monitor.json
- HTML version of this page: https://verifymcp.io/servers/com-mambabuilt-mcp-meta-ad-library-monitor/mambalabsdev-mcp-meta-ad-library-monitor
