Kagi Search vs Ca Procurement
Kagi Search is an MCP server published by kagisearch. Marketplaces we read that list it: 1 (Docker MCP Catalog). Ca Procurement is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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 |  Ca Procurement |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:c26439346cd6 Forks (GitHub): 49 Pulls (Docker Hub): 19 907 Stars (Docker Hub): 1 Stars (GitHub): 544 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.2 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 | Ca Procurement |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 544 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 19 907 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 49 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/kagisearch) | Remote server (gateway.pipeworx.io/ca-procurement/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/pipeworx-io/mcp-ca-procurement |
| 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 17 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.
Ca Procurement
California State Procurement MCP — State contract awards & purchase orders (keyless).
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)
Ca Procurement As a remote MCP server
claude mcp add --transport http ca-procurement https://gateway.pipeworx.io/ca-procurement/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Ca Procurement has a remote endpoint we check. How we check endpoints
Tools each declares
Only Kagi Search has
kagi_search_fetchkagi_summarizer
Only Ca Procurement has
ai_visibility_checkarchive_comparearchive_evidenceask_pipeworxask_pipeworx_betaask_pipeworx_groundedbet_researchca_procurement_awardsca_procurement_commoditiesca_procurement_departmentca_procurement_supplierca_procurement_top_suppliers
Show the remaining 33
classify_rowcompany_factscompare_entitiesdeep_researchdiscover_toolsentity_profileforgetgenerate_llms_txtkalshi_weather_edgelist_subscriptionspipeworx_feedbackpipeworx_trendingpolymarket_arbitragepolymarket_edge_trackerpolymarket_edgespolymarket_fill_riskpolymarket_kalshi_spreadrecallrecent_alertsrecent_changesrelease_calendar_marketsrememberresearch_rowresolution_auditresolution_diffresolve_entityscan_competitor_ai_presencescan_dependencysearch_withinsubscribesuggest_questionsunsubscribevalidate_claim
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Ca Procurement as of 2026-10-13). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of Ca Procurement publish no settings it asks for, so we do not compare settings.
What it can do: Kagi Search · What it can do: Ca Procurement · 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.