Google Ads Transparency Scraper vs Yandex Direct MCP
Google Ads Transparency Scraper is an MCP server published by CleanData-Labs. Marketplaces we read that list it: 1 (Official MCP Registry). Yandex Direct MCP is an MCP server published by askads. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Google Ads Transparency Scraper |  Yandex Direct MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 No figure published Not marked · First seen |
Listed Version: 1.13.1 Downloads/month (npm): 3 451 Downloads/week (npm): 2 071 Forks (GitHub): 2 Stars (GitHub): 4 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.13.1 Downloads/month (npm): 3 451 Downloads/week (npm): 2 071 Forks (GitHub): 2 Stars (GitHub): 4 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Google Ads Transparency Scraper | Yandex Direct MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 4 |
| Forks (GitHub) (differs) | No figure on GitHub | 2 |
| Last release (differs) | 2026-10-30 (worse) | 2026-11-06 (better) |
| Where it runs (differs) | Remote server (mcp.apify.com) | On your machine (mcp-yandex-direct) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 5, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | Not stated | github.com/askads/mcp-yandex-direct |
| Changes in the last 7 days (differs) | 0 | 5 |
| First seen (differs) | 2026-10-28 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 32 h ago returned HTTP 401 | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Google Ads Transparency Scraper
Competitor ads from Google Ads Transparency Center by brand or domain: ad text, YouTube IDs.
Yandex Direct MCP
MCP server for Yandex Direct API v5: manage PPC campaigns, ads, keywords, and statistics.
How to run each
Google Ads Transparency Scraper
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: Authorization header
Yandex Direct MCP As a local MCP server: npm package
claude mcp add --env "YANDEX_DIRECT_TOKEN=<YOUR_YANDEX_DIRECT_TOKEN>" --transport stdio mcp-yandex-direct -- npx -y mcp-yandex-directRequires: YANDEX_DIRECT_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Google Ads Transparency Scraper has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Google Ads Transparency Scraper publish no settings it asks for, so we do not compare settings.
What it can do: Google Ads Transparency Scraper · What it can do: Yandex Direct MCP · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.