Kagi Search vs Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs)
Kagi Search is an MCP server published by kagisearch. Marketplaces we read that list it: 1 (Docker MCP Catalog). Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs) is an MCP server published by curo.you. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. 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 |   Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs) |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:c26439346cd6 Forks (GitHub): 52 Pulls (Docker Hub): 20 494 Stars (Docker Hub): 1 Stars (GitHub): 563 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.5 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 | Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 563 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 20 494 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 52 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-11-03 |
| Where it runs (differs) | On your machine (mcp/kagisearch) | Remote server (mcp.curo.you/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/curo-you-peptides/peptide-research-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-11-02 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 10 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.
Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs)
Peptide research for your AI: PepBank study findings plus the curo.you peptide catalog and lot COAs.
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)
Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs) As a remote MCP server
claude mcp add --transport http peptide-research https://mcp.curo.you/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs) has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs) publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs) publish no settings it asks for, so we do not compare settings.
What it can do: Kagi Search · What it can do: Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs) · 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.