Comparison

Kagi Search vs io.github.Ninjabeam20/sportiq-mcp

Kagi Search is an MCP server published by kagisearch. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.Ninjabeam20/sportiq-mcp is an MCP server published by Ninjabeam20. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
Marketplace	Kagi Search	io.github.Ninjabeam20/sportiq-mcp
Docker MCP Catalog	Listed Version: sha256:c26439346cd6 Forks (GitHub): 51 Pulls (Docker Hub): 20 413 Stars (Docker Hub): 1 Stars (GitHub): 560 Not marked · First seen 2026-10-11	Not listed
Official MCP Registry	Not listed	Listed Version: 0.4.0 Downloads/month (PyPI): 175 Downloads/week (PyPI): 29 Forks (GitHub): 1 Stars (GitHub): 10 Not marked · First seen 2026-10-11

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 io.github.Ninjabeam20/sportiq-mcp
Fact	Kagi Search	io.github.Ninjabeam20/sportiq-mcp
Marketplaces that list it	1	1
Stars (GitHub) (differs)	560 (better)	10 (worse)
Pulls (Docker Hub) (differs)	20 413	No figure on Docker Hub
Forks (GitHub) (differs)	51 (better)	1 (worse)
Last release (differs)	Not published	2026-10-23
Where it runs (differs)	On your machine (mcp/kagisearch)	Remote server (sportiq.utkarshgupta.org/mcp)
Transport (differs)	stdio	Streamable HTTP
Tools it declares (differs)	2	Not published
Environment variables it asks for (differs)	2, secrets among them: 1	Not published
Licence (differs)	MIT	Not stated
Repository (differs)	github.com/kagisearch/kagimcp	github.com/ninjabeam20/sportiq-mcp
Changes in the last 7 days	0	0
First seen	2026-10-11	2026-10-11
Endpoint at the last check (differs)	no remote endpoint we check	Responded 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.

io.github.Ninjabeam20/sportiq-mcp

In its own words, on Official MCP Registry:

MCP tools for FIFA World Cup 2026 football, Formula 1, and IPL cricket — sims, strategy, fantasy.

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)

io.github.Ninjabeam20/sportiq-mcp As a remote MCP server

Claude Code

claude mcp add --transport http sportiq-mcp https://sportiq.utkarshgupta.org/mcp

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

Only io.github.Ninjabeam20/sportiq-mcp has a remote endpoint we check. How we check endpoints

Tools each declares

Only Kagi Search has

kagi_search_fetch
kagi_summarizer

Only io.github.Ninjabeam20/sportiq-mcp has

cricket_build_dream11_team
cricket_captain_recommendation
cricket_differential_picks
cricket_find_value_bets
cricket_get_live_matches
cricket_get_live_odds
cricket_get_pitch_report
cricket_get_points_table
cricket_get_schedule
cricket_get_scorecard
cricket_get_squad
cricket_head_to_head

Show the remaining 34

cricket_player_form_index
cricket_player_matchup
cross_sport_build_accumulator
f1_get_drivers
f1_get_lap_times
f1_get_race_results
f1_get_sessions
f1_get_standings
f1_get_weather
f1_head_to_head_pace
f1_predict_pit_strategy
f1_qualifying_analysis
f1_race_pace_compare
f1_simulate_championship
f1_tyre_degradation
f1_undercut_window
f1_weather_strategy_impact
football_build_accumulator
football_find_value_bets
football_form_trends
football_get_fixtures
football_get_groups
football_get_match_stats
football_get_odds
football_get_squad
football_get_standings
football_get_top_scorers
football_knockout_path
football_match_predictor
football_simulate_bracket
football_simulate_group
football_what_if
football_xg_model
sportiq_health

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (io.github.Ninjabeam20/sportiq-mcp as of 2026-11-05). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

The marketplaces of io.github.Ninjabeam20/sportiq-mcp publish no settings it asks for, so we do not compare settings.

What it can do: Kagi Search · What it can do: io.github.Ninjabeam20/sportiq-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 2026-11-09. We publish no contact details for plugin publishers.