adhistory: Google Ads, reviews, jobs, PDFs vs Google Ads Transparency (via Apify)
adhistory: Google Ads, reviews, jobs, PDFs is an MCP server published by OBrandon. Marketplaces we read that list it: 1 (Official MCP Registry). Google Ads Transparency (via Apify) is an MCP server published by retracn. Marketplaces we read that list it: 1 (Official MCP Registry). 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 |  adhistory: Google Ads, reviews, jobs, PDFs |   Google Ads Transparency (via Apify) |
|---|---|---|
| Official MCP Registry | Listed Version: 0.5.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | adhistory: Google Ads, reviews, jobs, PDFs | Google Ads Transparency (via Apify) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-11-09 | Not published |
| Where it runs (differs) | On your machine (adhistory-mcp) | Remote server (mcp.apify.com) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/obrandon/adhistory-mcp | github.com/retracn/google-ads-transparency-scraper |
| Changes in the last 7 days (differs) | 7 | 0 |
| First seen (differs) | 2026-11-07 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 32 h ago returned HTTP 401 |
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
adhistory: Google Ads, reviews, jobs, PDFs
Competitor Google ads, app reviews, job boards, PDF tables/invoices, email checks via Apify
Google Ads Transparency (via Apify)
Competitors' Google ads for AI agents: every ad a brand runs, with dates and ad text.
How to run each
adhistory: Google Ads, reviews, jobs, PDFs As a local MCP server: PyPI package
claude mcp add --env "APIFY_TOKEN=<YOUR_APIFY_TOKEN>" --transport stdio adhistory-mcp -- uvx adhistory-mcpRequires: APIFY_TOKEN (secret)
Google Ads Transparency (via Apify)
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Google Ads Transparency (via Apify) 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 (via Apify) publish no settings it asks for, so we do not compare settings.
What it can do: adhistory: Google Ads, reviews, jobs, PDFs · What it can do: Google Ads Transparency (via Apify) · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.