Ext Ops Panel
Open dashboard
Comparison

io.flipzi/flipzi-mcp vs Kalshi Kernel

io.flipzi/flipzi-mcp is an MCP server published by flipzi.io. Marketplaces we read that list it: 1 (Official MCP Registry). Kalshi Kernel is an MCP server published by copyleftdev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
Marketplaceio.flipzi/flipzi-mcpKalshi Kernel
Official MCP Registry Listed
Version: 0.1.1
Downloads/month (npm): 305
Downloads/week (npm): 26
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.1
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

io.flipzi/flipzi-mcp vs Kalshi Kernel
Factio.flipzi/flipzi-mcpKalshi Kernel
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)2026-10-14Not published
Where it runs (differs)On your machine (@flipzitcg/mcp)On your machine (ghcr.io/copyleftdev/kalshi-kernel:0.1.1)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 14, secrets among them: 1
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/flipzitcg/flipzi-mcpgithub.com/copyleftdev/kalshi-kernel
Changes in the last 7 days00
First seen (differs)2026-10-142026-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

io.flipzi/flipzi-mcp

In its own words, on Official MCP Registry:

Trading card prices, sold comps, history and movers from the Flipzi Data API. Bring your own key.

Kalshi Kernel

In its own words, on Official MCP Registry:

Unofficial safety-focused MCP server for Kalshi market data and explicitly authorized trading

How to run each

io.flipzi/flipzi-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "FLIPZI_API_KEY=<YOUR_FLIPZI_API_KEY>" --transport stdio flipzi-mcp -- npx -y @flipzitcg/mcp

Requires: FLIPZI_API_KEY (secret)

Kalshi Kernel As a local MCP server: Docker image

Claude Code
claude mcp add --env "KALSHI_API_KEY_ID=<YOUR_KALSHI_API_KEY_ID>" --transport stdio kalshi-kernel -- docker run -i --rm -e KALSHI_API_KEY_ID ghcr.io/copyleftdev/kalshi-kernel:0.1.1

Requires: KALSHI_API_KEY_ID (secret)

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only io.flipzi/flipzi-mcp asks for

  • FLIPZI_API_KEY (secret)

Only Kalshi Kernel asks for

  • KALSHI_API_KEY_ID (secret)
  • KALSHI_KERNEL_MODE
  • KALSHI_LIVE_TRADING_ACK
  • KALSHI_PRIVATE_KEY_PATH

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.flipzi/flipzi-mcp · What it can do: Kalshi Kernel · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built