Trendzeist – Google Trends for content ideation vs Google Trends
Trendzeist – Google Trends for content ideation is an MCP server published by phalkmin. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). Google Trends is an MCP server published by wulfcare. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-13. 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 |  Trendzeist – Google Trends for content ideation |  Google Trends |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.1 Downloads/month (PyPI): 1 532 Downloads/week (PyPI): 1 144 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 0.6.1 Downloads/month (PyPI): 1 532 Downloads/week (PyPI): 1 144 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
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 | Trendzeist – Google Trends for content ideation | Google Trends |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 3 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-11-05 | Not published |
| Where it runs (differs) | On your machine (trendzeist-mcp) | Remote server (mcp.apify.com) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/phalkmin/trendzeist-mcp | github.com/wulfcare/scrapers |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-10 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 9 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
Trendzeist – Google Trends for content ideation
Free Google Trends MCP: ranked breakout/rising/evergreen topics for content ideas. No API key.
Google Trends
Google Trends interest over time, by region, related queries, plus Trending Now.
How to run each
Trendzeist – Google Trends for content ideation As a local MCP server: PyPI package
claude mcp add --env "TRENDZEIST_PROXIES=<YOUR_TRENDZEIST_PROXIES>" --transport stdio trendzeist-mcp -- uvx trendzeist-mcpRequires: TRENDZEIST_PROXIES (secret)
Google Trends
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 Trends 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 Trends publish no settings it asks for, so we do not compare settings.
What it can do: Trendzeist – Google Trends for content ideation · What it can do: Google Trends · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.