waldo-fyi vs Google data (Trends, YouTube, Ads Transparency, Play)
waldo-fyi is a plugin bundle for AI coding tools published by waldo-fyi. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Google data (Trends, YouTube, Ads Transparency, Play) is an MCP server published by ducnhd. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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 |  waldo-fyi |  Google data (Trends, YouTube, Ads Transparency, Play) |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.4.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.0 Downloads/month (PyPI): 95 Downloads/week (PyPI): 41 Forks (GitHub): 0 Stars (GitHub): 2 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 | waldo-fyi | Google data (Trends, YouTube, Ads Transparency, Play) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 2 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.waldo.fyi/strategy) | On your machine (google-data-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 18 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/waldo-fyi/waldo-claude-plugin | github.com/ducnhd/google-data-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 10 h ago | 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
waldo-fyi
Waldo strategy agent skills for ad intelligence, social listening, web research, data analysis, and archival knowledge — powered by the Waldo MCP connector
Google data (Trends, YouTube, Ads Transparency, Play)
Google Trends, YouTube, Ads Transparency and Play reviews over plain HTTP. No API key.
How to run each
waldo-fyi As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install waldo-fyi@claude-communityGoogle data (Trends, YouTube, Ads Transparency, Play) As a local MCP server: PyPI package
claude mcp add --transport stdio google-data-mcp -- uvx google-data-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only waldo-fyi 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: waldo-fyi · What it can do: Google data (Trends, YouTube, Ads Transparency, Play) · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.