Ext Ops Panel
Open dashboard
Comparison

google-ads-transparency-mcp vs Meta Ad Library Spend MCP by AdSpendSpy

google-ads-transparency-mcp is an MCP server published by block-town. Marketplaces we read that list it: 1 (PyPI (MCP servers)). Meta Ad Library Spend MCP by AdSpendSpy is an MCP server published by adspendspy.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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
Marketplacegoogle-ads-transparency-mcpMeta Ad Library Spend MCP by AdSpendSpy
PyPI (MCP servers) Listed
Version: 0.3.0
Downloads/month (PyPI): 1 067
Downloads/week (PyPI): 292
Forks (GitHub): 4
Stars (GitHub): 14
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.2
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

google-ads-transparency-mcp vs Meta Ad Library Spend MCP by AdSpendSpy
Factgoogle-ads-transparency-mcpMeta Ad Library Spend MCP by AdSpendSpy
Marketplaces that list it11
Stars (GitHub) (differs)14No figure on GitHub
Forks (GitHub) (differs)4No figure on GitHub
Last release (differs)Not published2026-10-23
Where it runs (differs)On your machine (google-ads-transparency-mcp)Remote server (www.adspendspy.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/block-town/google-ads-transparency-mcpNot stated
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-22
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 h ago

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-mcp

In its own words, on PyPI (MCP servers):

MCP server for the Google Ads Transparency Center — look up any advertiser's ads without an API key

Meta Ad Library Spend MCP by AdSpendSpy

In its own words, on Official MCP Registry:

Facebook and Meta Ad Library ads with estimated ad spend per ad, top landing pages and alerts.

How to run each

google-ads-transparency-mcp

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Meta Ad Library Spend MCP by AdSpendSpy As a remote MCP server

Claude Code
claude mcp add --transport http adspendspy https://www.adspendspy.com/mcp --header "X-API-Key: <YOUR_X_API_KEY>"

Requires: X-API-Key header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Meta Ad Library Spend MCP by AdSpendSpy 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

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

What it can do: google-ads-transparency-mcp · What it can do: Meta Ad Library Spend MCP by AdSpendSpy · Compare two other plugins

Package data comes from the Python Package Index (pypi.org). 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