Kagi Search vs FHIR MCP Server
Kagi Search is an MCP server published by kagisearch. Marketplaces we read that list it: 1 (Docker MCP Catalog). FHIR MCP Server is an MCP server published by wso2. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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 |  FHIR MCP Server |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:c26439346cd6 Forks (GitHub): 49 Pulls (Docker Hub): 19 895 Stars (Docker Hub): 1 Stars (GitHub): 544 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.10.0 Downloads/month (PyPI): 456 Downloads/week (PyPI): 222 Forks (GitHub): 58 Stars (GitHub): 137 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 | FHIR MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 544 (better) | 137 (worse) |
| Pulls (Docker Hub) (differs) | 19 895 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 49 (worse) | 58 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/kagisearch) | On your machine (fhir-mcp-server) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 2 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 1, secrets among them: 0 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/kagisearch/kagimcp | github.com/wso2/fhir-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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.
FHIR MCP Server
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
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)
FHIR MCP Server As a local MCP server: PyPI package
claude mcp add --env "FHIR_SERVER_BASE_URL=<YOUR_FHIR_SERVER_BASE_URL>" --transport stdio fhir-mcp-server -- uvx fhir-mcp-serverRequires: FHIR_SERVER_BASE_URL
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of FHIR MCP Server 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 FHIR MCP Server asks for
FHIR_SERVER_BASE_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Kagi Search · What it can do: FHIR MCP Server · 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.