apify vs Superdemands: Google Search Trends & Demand
apify is a plugin bundle for AI coding tools published by apify. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). Superdemands: Google Search Trends & Demand is an MCP server published by superdemands.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-14. 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 |  apify |   Superdemands: Google Search Trends & Demand |
|---|---|---|
| Copilot CLI: github/awesome-copilot | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | 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 | apify | Superdemands: Google Search Trends & Demand |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (superdemands.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/apify/apify-github-copilot-plugin | github.com/superdemands/google-search-trends-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-21 |
| Endpoint at the last check (differs) | no remote endpoint we check | No HTTP response at the last check (11 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
apify
Helps devs extract data from any website with thousands of trusted scrapers, crawlers, and automations from Apify Store. Integrate ready-made Actors to access all popular social media, video, e-commerce, search engines, maps, and travel sites. Build, debug, publish, and monetize new Actors on Apify.
Superdemands: Google Search Trends & Demand
Google search trends and search demand: 5 years of interest, momentum and seasonality per topic
How to run each
apify
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Superdemands: Google Search Trends & Demand As a remote MCP server
claude mcp add --transport http search-demand https://superdemands.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Superdemands: Google Search Trends & Demand 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: apify · What it can do: Superdemands: Google Search Trends & Demand · Compare two other plugins
Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/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.