Kagi Search vs io.github.SeoScoreAPI/seoscoreapi-mcp
Kagi Search is an MCP server published by kagisearch. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.SeoScoreAPI/seoscoreapi-mcp is an MCP server published by SeoScoreAPI. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:c26439346cd6 Forks (GitHub): 48 Pulls (Docker Hub): 19 843 Stars (Docker Hub): 1 Stars (GitHub): 541 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.4.1 Downloads/month (npm): 651 Downloads/week (npm): 434 Forks (GitHub): 0 Stars (GitHub): 0 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 | io.github.SeoScoreAPI/seoscoreapi-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 541 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 19 843 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 48 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/kagisearch) | On your machine (seoscoreapi-mcp) |
| 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: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/kagisearch/kagimcp | github.com/seoscoreapi/seoscoreapi-mcp |
| 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.
io.github.SeoScoreAPI/seoscoreapi-mcp
SEO audits, AI readability, accessibility, backlinks and score monitoring from SEO Score API.
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/kagisearch
Requires: KAGI_API_KEY (secret)
io.github.SeoScoreAPI/seoscoreapi-mcp As a local MCP server: npm package
claude mcp add --env "SEO_SCORE_API_KEY=<YOUR_SEO_SCORE_API_KEY>" --transport stdio seoscoreapi-mcp -- npx -y seoscoreapi-mcp
Requires: SEO_SCORE_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 io.github.SeoScoreAPI/seoscoreapi-mcp 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 io.github.SeoScoreAPI/seoscoreapi-mcp asks for
SEO_SCORE_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: io.github.SeoScoreAPI/seoscoreapi-mcp · 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.