io.github.den-indance/google-trends-mcp vs Steadyfetch actors on Apify MCP
io.github.den-indance/google-trends-mcp is an MCP server published by den-indance. Marketplaces we read that list it: 1 (Official MCP Registry). Steadyfetch actors on Apify MCP is an MCP server published by steadyfetch. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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 |  io.github.den-indance/google-trends-mcp |  Steadyfetch actors on Apify MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Downloads/month (npm): 144 Downloads/week (npm): 20 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | io.github.den-indance/google-trends-mcp | Steadyfetch actors on Apify MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@den.dance/google-trends-mcp) | Remote server (mcp.apify.com) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 2 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/den-indance/google-trends-mcp | github.com/steadyfetch/steadyfetch-agent-tools |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-24 |
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
io.github.den-indance/google-trends-mcp
Google Trends MCP with proxy rotation, auto-retry on Google blocks, residential-proxy setup.
Steadyfetch actors on Apify MCP
Apify MCP pinned to 30 Steadyfetch actors: ad, video and audio transcripts, trends, jobs, Amazon
How to run each
io.github.den-indance/google-trends-mcp As a local MCP server: npm package
claude mcp add --env "PROXY_LIST=<YOUR_PROXY_LIST>" --env "PROXY_URL=<YOUR_PROXY_URL>" --transport stdio google-trends-mcp -- npx -y @den.dance/google-trends-mcpRequires: PROXY_LIST (secret), PROXY_URL (secret)
Steadyfetch actors on Apify MCP
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 Steadyfetch actors on Apify MCP 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 Steadyfetch actors on Apify MCP publish no settings it asks for, so we do not compare settings.
What it can do: io.github.den-indance/google-trends-mcp · What it can do: Steadyfetch actors on Apify MCP · Compare two other plugins
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.