Swellmeter: Google Trends Rising Queries & Verdicts vs New-Term Radar
Swellmeter: Google Trends Rising Queries & Verdicts is an MCP server published by cybermax.cybermax-tools.workers.dev. Marketplaces we read that list it: 1 (Official MCP Registry). New-Term Radar is an MCP server published by zhuyansen. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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 |  Swellmeter: Google Trends Rising Queries & Verdicts |  New-Term Radar |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 0.6.1 Downloads/month (PyPI): 0 Downloads/week (PyPI): 159 Forks (GitHub): 646 Stars (GitHub): 2 168 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 | Swellmeter: Google Trends Rising Queries & Verdicts | New-Term Radar |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 2 168 |
| Forks (GitHub) (differs) | No figure on GitHub | 646 |
| Last release (differs) | Not published | 2026-10-29 |
| Where it runs (differs) | Remote server (mcp.apify.com) | On your machine (new-term-radar) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 2 |
| Parts of the bundle (differs) | Not a bundle | 4 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | Not stated | github.com/zhuyansen/new-term-radar |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-11-10 | 2026-10-18 |
| Endpoint at the last check (differs) | Responded 9 h ago, requires authentication | no 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
Swellmeter: Google Trends Rising Queries & Verdicts
Swellmeter: Google Trends verdict, % change, rising and breakout queries per keyword.
New-Term Radar
New AI model, product and repo names as they surface, and the search terms behind them, sized.
How to run each
Swellmeter: Google Trends Rising Queries & Verdicts
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: Authorization header
New-Term Radar As a local MCP server: PyPI package
claude mcp add --env "AISA_API_KEY=<YOUR_AISA_API_KEY>" --env "GOANYAPI_API_KEY=<YOUR_GOANYAPI_API_KEY>" --transport stdio new-term-radar -- uvx --with mcp new-term-radar mcpRequires: AISA_API_KEY (secret), GOANYAPI_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Swellmeter: Google Trends Rising Queries & Verdicts 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 Swellmeter: Google Trends Rising Queries & Verdicts publish no settings it asks for, so we do not compare settings.
What it can do: Swellmeter: Google Trends Rising Queries & Verdicts · What it can do: New-Term Radar · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.