Kagi Search vs LienDeadline
Kagi Search is an MCP server published by kagisearch. Marketplaces we read that list it: 1 (Docker MCP Catalog). LienDeadline is an MCP server published by LienDeadline. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-21. 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 |   LienDeadline |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:c26439346cd6 Forks (GitHub): 49 Pulls (Docker Hub): 19 946 Stars (Docker Hub): 1 Stars (GitHub): 546 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.5.5 Downloads/month (npm): 1 968 Downloads/week (npm): 914 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.5.5 Downloads/month (npm): 1 968 Downloads/week (npm): 914 Forks (GitHub): 0 Stars (GitHub): 1 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 | LienDeadline |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 546 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 19 946 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 49 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-21 |
| Where it runs (differs) | On your machine (mcp/kagisearch) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 2 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 1, secrets among them: 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/kagisearch/kagimcp | github.com/liendeadline/liendeadline-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 23 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
The Official Model Context Protocol (MCP) server for Kagi Search & other tools.
LienDeadline
Statute-cited lien and notice deadlines for material suppliers; lien guides for 50 states and DC.
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)
LienDeadline As a remote MCP server
claude mcp add --transport http liendeadline-mcp https://mcp.liendeadline.com/mcpRequires: LIENDEADLINE_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only LienDeadline has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of LienDeadline 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 LienDeadline asks for
LIENDEADLINE_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: LienDeadline · 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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.