Ext Ops Panel
Open dashboard
Comparison

Kagi Search vs OrionCMD Checks

Kagi Search is an MCP server published by kagisearch. Marketplaces we read that list it: 1 (Docker MCP Catalog). OrionCMD Checks is an MCP server published by api.orioncmd.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-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

Where each is published
MarketplaceKagi SearchOrionCMD Checks
Docker MCP Catalog Listed
Version: sha256:c26439346cd6
Forks (GitHub): 49
Pulls (Docker Hub): 19 852
Stars (Docker Hub): 1
Stars (GitHub): 542
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.4.0
No figure published
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 OrionCMD Checks
FactKagi SearchOrionCMD Checks
Marketplaces that list it11
Stars (GitHub) (differs)542No figure on GitHub
Pulls (Docker Hub) (differs)19 852No figure on Docker Hub
Forks (GitHub) (differs)49No figure on GitHub
Last release (differs)Not published2026-10-14
Where it runs (differs)On your machine (mcp/kagisearch)Remote server (api.orioncmd.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)2Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/kagisearch/kagimcpNot stated
Changes in the last 7 days (differs)04
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 25 h ago

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.

OrionCMD Checks

In its own words, on Official MCP Registry:

Pay-per-call TLS, DNS/email-auth and expiry checks, plus a $2 full site audit (x402 USDC).

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)

OrionCMD Checks As a remote MCP server

Claude Code
claude mcp add --transport http checks https://api.orioncmd.com/mcp

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

Only OrionCMD Checks has a remote endpoint we check. How we check endpoints

Tools each declares

Only Kagi Search has

  • kagi_search_fetch
  • kagi_summarizer

Only OrionCMD Checks has

  • check_cert
  • check_dns
  • check_domain_expiry
  • check_email_auth
  • check_security_headers
  • domain_grade
  • full_site_audit
  • pricing
  • site_health
  • validate_target

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (OrionCMD Checks as of 2026-10-14). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

The marketplaces of OrionCMD Checks publish no settings it asks for, so we do not compare settings.

What it can do: Kagi Search · What it can do: OrionCMD Checks · 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