Ext Ops Panel
Open dashboard
Comparison

Kagi Search vs geo-score

Kagi Search is an MCP server published by kagisearch. Marketplaces we read that list it: 1 (Docker MCP Catalog). geo-score is an MCP server published by jianruntech. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
MarketplaceKagi Searchgeo-score
Docker MCP Catalog Listed
Version: sha256:c26439346cd6
Forks (GitHub): 49
Pulls (Docker Hub): 19 870
Stars (Docker Hub): 1
Stars (GitHub): 543
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.8.3
Downloads/month (PyPI): 490
Downloads/week (PyPI): 244
Forks (GitHub): 9
Stars (GitHub): 323
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

Kagi Search vs geo-score
FactKagi Searchgeo-score
Marketplaces that list it11
Stars (GitHub) (differs)543 (better)323 (worse)
Pulls (Docker Hub) (differs)19 870No figure on Docker Hub
Forks (GitHub) (differs)49 (better)9 (worse)
Last release (differs)Not published2026-10-15
Where it runs (differs)On your machine (mcp/kagisearch)On your machine (geo-score)
Transportstdiostdio
Tools it declares (differs)2Not published
Environment variables it asks for (differs)2, secrets among them: 16, secrets among them: 5
Licence (differs)MITNot stated
Repository (differs)github.com/kagisearch/kagimcpgithub.com/jianruntech/geo-score
Changes in the last 7 days (differs)04
First seen (differs)2026-10-112026-10-12

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

In its own words, on Docker MCP Catalog:

The Official Model Context Protocol (MCP) server for Kagi Search & other tools.

geo-score

In its own words, on Official MCP Registry:

Free 0-100 score: can AI engines cite a site? Plus citation checks with your own API keys.

How to run each

Kagi Search As a local MCP server: Docker image

Claude Code
claude mcp add --env "KAGI_API_KEY=<YOUR_KAGI_API_KEY>" --transport stdio kagisearch -- docker run -i --rm -e KAGI_API_KEY mcp/kagisearch

Requires: KAGI_API_KEY (secret)

geo-score As a local MCP server: PyPI package

Claude Code
claude mcp add --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --env "OPENROUTER_API_KEY=<YOUR_OPENROUTER_API_KEY>" --env "PERPLEXITY_API_KEY=<YOUR_PERPLEXITY_API_KEY>" --transport stdio geo-score -- uvx geo-score mcp

Requires: ANTHROPIC_API_KEY (secret), GEMINI_API_KEY (secret), OPENAI_API_KEY (secret), OPENROUTER_API_KEY (secret), PERPLEXITY_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 geo-score 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 geo-score asks for

  • ANTHROPIC_API_KEY (secret)
  • GEMINI_API_KEY (secret)
  • GEO_SCORE_WATCH_CONFIG
  • OPENAI_API_KEY (secret)
  • OPENROUTER_API_KEY (secret)
  • PERPLEXITY_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Kagi Search · What it can do: geo-score · 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. 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