OECD MCP Server vs Google Trends (via Apify)
OECD MCP Server is an MCP server published by isakskogstad. Marketplaces we read that list it: 1 (Official MCP Registry). Google Trends (via Apify) is an MCP server published by retracn. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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 |  OECD MCP Server |   Google Trends (via Apify) |
|---|---|---|
| Official MCP Registry | Listed Version: 3.0.0 Forks (GitHub): 5 Stars (GitHub): 8 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 | OECD MCP Server | Google Trends (via Apify) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 8 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 5 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (oecd-mcp-server.onrender.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/isakskogstad/oecd-mcp-server | github.com/retracn/google-trends-scraper |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 38 h ago returned HTTP 503 | Status out of date: last check 39 h ago returned HTTP 401 |
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
OECD MCP Server
OECD economic and statistical data via SDMX API. Access 5,000+ datasets across 17 categories.
Google Trends (via Apify)
Google Trends data for AI agents: interest over time, regions, rising queries and trending searches.
How to run each
OECD MCP Server As a remote MCP server
claude mcp add --transport http oecd-mcp https://oecd-mcp-server.onrender.com/mcpGoogle Trends (via Apify)
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 Google Trends (via Apify) 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: OECD MCP Server · What it can do: Google Trends (via Apify) · 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.