Superdemands: Google Search Trends & Demand vs fairfetch: web data tools for AI agents, priced per result
Superdemands: Google Search Trends & Demand is an MCP server published by superdemands.com. Marketplaces we read that list it: 1 (Official MCP Registry). fairfetch: web data tools for AI agents, priced per result is an MCP server published by fairfetch-data. 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 |   Superdemands: Google Search Trends & Demand |   fairfetch: web data tools for AI agents, priced per result |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | Superdemands: Google Search Trends & Demand | fairfetch: web data tools for AI agents, priced per result |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (superdemands.com/mcp) | Remote server (mcp.apify.com) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/superdemands/google-search-trends-mcp | github.com/fairfetch-data/fairfetch-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-21 | 2026-10-23 |
| Endpoint at the last check (differs) | No HTTP response at the last check (11 h ago) | Responded 8 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
Superdemands: Google Search Trends & Demand
Google search trends and search demand: 5 years of interest, momentum and seasonality per topic
fairfetch: web data tools for AI agents, priced per result
Google Trends & Ads Transparency Center, keywords, apps, jobs, events, docs, screenshots, groceries
How to run each
Superdemands: Google Search Trends & Demand As a remote MCP server
claude mcp add --transport http search-demand https://superdemands.com/mcpfairfetch: web data tools for AI agents, priced per result
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 the endpoint of fairfetch: web data tools for AI agents, priced per result responded at the last daily 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: Superdemands: Google Search Trends & Demand · What it can do: fairfetch: web data tools for AI agents, priced per result · 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.