Ext Ops Panel
Open dashboard
Comparison

exa vs Google Trends

exa is a plugin bundle for AI coding tools published by exa-labs. Marketplaces we read that list it: 4 (Claude Code: claude-plugins-official, Official MCP Registry, Docker MCP Catalog, Claude: knowledge-work-plugins). Google Trends is an MCP server published by mamrrez. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. 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

Where each is published
MarketplaceexaGoogle Trends
Claude Code: claude-plugins-official Listed
Version: 3.4.1
Forks (GitHub): 409
Stars (GitHub): 5 212
Not marked · First seen
Not listed
Official MCP Registry Listed
Version: 3.4.1
Forks (GitHub): 409
Stars (GitHub): 5 212
Not marked · First seen
Listed
Version: 0.1.1
Downloads/month (PyPI): 355
Downloads/week (PyPI): 55
Forks (GitHub): 0
Stars (GitHub): 4
Not marked · First seen
Docker MCP Catalog Listed
Version: sha256:d88edd571d98
Forks (GitHub): 409
Pulls (Docker Hub): 37 638
Stars (Docker Hub): 7
Stars (GitHub): 5 212
Not marked · First seen
Not listed
Claude: knowledge-work-plugins Listed
Version: 3.4.1
Forks (GitHub): 409
Stars (GitHub): 5 212
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

exa vs Google Trends
FactexaGoogle Trends
Marketplaces that list it (differs)4 (better)1 (worse)
Stars (GitHub) (differs)5 212 (better)4 (worse)
Pulls (Docker Hub) (differs)37 638No figure on Docker Hub
Forks (GitHub) (differs)409 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server or your machineOn your machine (gtrends-mcp-full)
Transport (differs)Streamable HTTP, stdiostdio
Tools it declares (differs)2Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)3Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/exa-labs/exa-mcp-servergithub.com/mamrrez/gtrends-mcp-full
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Status out of date: last check 6 days ago returned HTTP 405no remote endpoint we check

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

exa

In its own words, on Claude Code: claude-plugins-official:

Exa AI web search, deep research, and content extraction. Provides MCP tools and research skills for comprehensive web search, people discovery, company research, academic papers, and more.

Google Trends

In its own words, on Official MCP Registry:

Google Trends: Trending Now, interest over time, regions, related searches. No API key.

How to run each

exa As a Claude Code plugin

Claude Code
/plugin install exa@claude-plugins-official

Google Trends As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio gtrends-mcp-full -- uvx gtrends-mcp-full

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only exa has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Google Trends publish no list of tools, so we do not compare tools.

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: exa · What it can do: Google Trends · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built