Ext Ops Panel
Open dashboard
Comparison

OSP Marketing Tools vs Google Ads Transparency Scraper & Monitor

OSP Marketing Tools is an MCP server published by open-strategy-partners. Marketplaces we read that list it: 1 (Docker MCP Catalog). Google Ads Transparency Scraper & Monitor is an MCP server published by akhilrajesh213. 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

Where each is published
MarketplaceOSP Marketing ToolsGoogle Ads Transparency Scraper & Monitor
Docker MCP Catalog Listed
Version: sha256:34b72f4cc3d2
Forks (GitHub): 43
Pulls (Docker Hub): 44 858
Stars (Docker Hub): 2
Stars (GitHub): 274
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.13
No figure published
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

OSP Marketing Tools vs Google Ads Transparency Scraper & Monitor
FactOSP Marketing ToolsGoogle Ads Transparency Scraper & Monitor
Marketplaces that list it11
Stars (GitHub) (differs)274No figure on GitHub
Pulls (Docker Hub) (differs)44 858No figure on Docker Hub
Forks (GitHub) (differs)43No figure on GitHub
Last release (differs)Not published2026-11-03
Where it runs (differs)On your machine (mcp/osp_marketing_tools)Remote server (akhil-rajesh--google-ads-transparency-scraper.apify.actor/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)6Not published
Environment variables it asks forNot publishedNot published
Licence (differs)CC-BY-SA-4.0Not stated
Repository (differs)github.com/open-strategy-partners/osp_marketing_toolsNot stated
Changes in the last 7 days (differs)01
First seen (differs)2026-10-112026-10-27
Endpoint at the last check (differs)no remote endpoint we checkResponded 8 h ago, requires authentication

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

OSP Marketing Tools

In its own words, on Docker MCP Catalog:

A Model Context Protocol (MCP) server that empowers LLMs to use some of Open Srategy Partners' core writing and product marketing techniques.

Google Ads Transparency Scraper & Monitor

In its own words, on Official MCP Registry:

Google Ads Transparency Center for AI agents: brands' ads, ad copy, political ad spend, removed ads.

How to run each

OSP Marketing Tools As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio osp-marketing-tools -- docker run -i --rm mcp/osp_marketing_tools

Google Ads Transparency Scraper & Monitor As a remote MCP server

Claude Code
claude mcp add --transport http google-ads-transparency https://akhil-rajesh--google-ads-transparency-scraper.apify.actor/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

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 Scraper & Monitor has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Google Ads Transparency Scraper & Monitor publish no list of tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: OSP Marketing Tools · What it can do: Google Ads Transparency Scraper & Monitor · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.

Where the data comes from: how the catalog is built