Ext Ops Panel
Open dashboard
Comparison

Kagi Search vs Horosa 星阙 — 术数 / 占星

Kagi Search is an MCP server published by kagisearch. Marketplaces we read that list it: 1 (Docker MCP Catalog). Horosa 星阙 — 术数 / 占星 is a plugin bundle for AI coding tools published by Horace Maxwell. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-22. 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 SearchHorosa 星阙 — 术数 / 占星
Docker MCP Catalog Listed
Version: sha256:c26439346cd6
Forks (GitHub): 49
Pulls (Docker Hub): 19 949
Stars (Docker Hub): 1
Stars (GitHub): 546
Not marked · First seen
Not listed
Community marketplace horace-maxwell/horosa-skill Not listed Listed
Version: 0.41.2
Forks (GitHub): 85
Stars (GitHub): 471
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 Horosa 星阙 — 术数 / 占星
FactKagi SearchHorosa 星阙 — 术数 / 占星
Marketplaces that list it11
Stars (GitHub) (differs)546 (better)471 (worse)
Pulls (Docker Hub) (differs)19 949No figure on Docker Hub
Forks (GitHub) (differs)49 (worse)85 (better)
Last release (differs)Not published2026-10-21
Where it runs (differs)On your machine (mcp/kagisearch)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)2Not published
Environment variables it asks for (differs)2, secrets among them: 16, secrets among them: 1
Parts of the bundle (differs)Not a bundle2
Licence (differs)MITAGPL-3.0-only
Repository (differs)github.com/kagisearch/kagimcpgithub.com/horace-maxwell/horosa-skill
Changes in the last 7 days (differs)03
First seen (differs)2026-10-112026-10-21

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.

Horosa 星阙 — 术数 / 占星

In its own words, on Community GitHub marketplaces:

110 local Horosa (星阙) technique tools over MCP + the horosa-agent skill (clarify-before-call gate, export-snapshot reading). Requires the offline runtime once: `uv run --directory <plugin dir>/horosa-skill horosa-skill install` (plugin dir = ~/.claude/plugins/cache/horosa-skill/horosa/<version>) (any `runtime.not_installed` error prints this command with the real path).

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)

Horosa 星阙 — 术数 / 占星 As a Claude Code plugin

Claude Code
/plugin marketplace add horace-maxwell/horosa-skill
/plugin install horosa@horosa-skill

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

Tools each declares

The marketplaces of Horosa 星阙 — 术数 / 占星 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 Horosa 星阙 — 术数 / 占星 asks for

  • HOROSA_INSTALL_CONTEXT
  • HOROSA_JEV
  • HOROSA_JEV_API_KEY (secret)
  • HOROSA_PLUGIN_ROOT
  • HOROSA_RUNTIME_ROOT
  • HOROSA_SKILL_DATA_DIR

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

What it can do: Kagi Search · What it can do: Horosa 星阙 — 术数 / 占星 · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.

Where the data comes from: how the catalog is built