Google Ads Transparency Monitor MCP Server
Related Servers
Alternatives to Google Ads Transparency Monitor MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables users to search the Google Ads Transparency Center for company ads, inspect ad details and variations, analyze images and videos, and compare competitor advertising strategies.3 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to look up which Google ads a competitor is running by domain, advertiser ID, Transparency Center link, or exact advertiser name, returning each ad's status, dates, days shown, and link with optional country and status filters.MIT
- FlicenseNot gradedqualityBmaintenanceEnables querying Google Ads Transparency data for advertiser suggestions, creatives, and ad history through a hosted API with built-in anti-bot handling.-
- AlicenseAqualityBmaintenanceAn MCP server that lets AI assistants look up any advertiser's Google ads. Search by domain or company name, retrieve ad creatives, and decode text ad content from Google's Ads Transparency Center.8292 PyPI14MIT
- AlicenseNot gradedqualityDmaintenanceSearches and analyzes competitor ads and content across Meta, Google, Instagram, TikTok, and YouTube with AI-powered creative analysis and cross-platform brand discovery.1MIT
- AlicenseAqualityCmaintenanceEnables searching and analyzing LinkedIn's public ad library for any company, including ad creatives, targeting, and competitive insights. Supports image and video analysis, company comparisons, and detailed ad lookups via natural language.76 npm3MIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of selecting the wrong one. Its purpose (fetching Google Ads Transparency Center data) is unambiguous.
The single tool follows a clear verb_noun pattern (get_google_ads). With only one name there is nothing to be inconsistent with.
One tool is thin for a named 'server', though the domain (read-only ad lookup) is narrow enough that a single flexible tool handling domains, names, and lists is defensible. It sits at the borderline where more granular operations (e.g. per-format or per-advertiser queries) might be expected.
For a read-only transparency lookup, the surface covers the key needs: ad rows, per-company summaries, status rows for no-ads/blocked/changed pages, and error reporting with run IDs. Only minor gaps remain, such as no explicit filtering or historical-comparison operation.