Kagi Search vs New-Term Radar
Kagi Search is an MCP server published by kagisearch. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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-10-29. 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 |  Kagi Search |  New-Term Radar |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:c26439346cd6 Forks (GitHub): 50 Pulls (Docker Hub): 20 238 Stars (Docker Hub): 1 Stars (GitHub): 550 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.6.1 Downloads/month (PyPI): 0 Downloads/week (PyPI): 444 Forks (GitHub): 591 Stars (GitHub): 1 902 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 | Kagi Search | New-Term Radar |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 550 (worse) | 1 902 (better) |
| Pulls (Docker Hub) (differs) | 20 238 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 50 (worse) | 591 (better) |
| Last release (differs) | Not published | 2026-10-28 |
| Where it runs (differs) | On your machine (mcp/kagisearch) | On your machine (new-term-radar) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 2 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 4, secrets among them: 2 |
| Parts of the bundle (differs) | Not a bundle | 4 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/kagisearch/kagimcp | github.com/zhuyansen/new-term-radar |
| Changes in the last 7 days (differs) | 0 | 6 |
| First seen (differs) | 2026-10-11 | 2026-10-18 |
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
Kagi Search
The Official Model Context Protocol (MCP) server for Kagi Search & other tools.
New-Term Radar
New AI model, product and repo names as they surface, and the search terms behind them, sized.
How to run each
Kagi Search As a local MCP server: Docker image
claude mcp add --env "KAGI_API_KEY=<YOUR_KAGI_API_KEY>" --transport stdio kagisearch -- docker run -i --rm -e KAGI_API_KEY mcp/kagisearchRequires: KAGI_API_KEY (secret)
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.
Tools each declares
The marketplaces of New-Term Radar publish no list of tools, so we do not compare tools.
Settings each asks for
Only Kagi Search asks for
KAGI_API_KEY (secret)KAGI_SUMMARIZER_ENGINE
Only New-Term Radar asks for
AISA_API_KEY (secret)GOANYAPI_API_KEY (secret)RADAR_CONFIGRADAR_STATE
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Kagi Search · What it can do: New-Term Radar · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.