Ext Ops Panel
Open dashboard
Comparison

vulcan vs Kalshi Kernel

vulcan is a plugin bundle for AI coding tools published by Ellipsis-Labs. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Kalshi Kernel is an MCP server published by copyleftdev. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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

Where each is published
MarketplacevulcanKalshi Kernel
Claude Code: claude-plugins-community Listed
Version: 0.5.0
Forks (GitHub): 6
Stars (GitHub): 20
Not marked · First seen
Not listed
Official MCP Registry Not listed 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

vulcan vs Kalshi Kernel
FactvulcanKalshi Kernel
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)20 (better)0 (worse)
Forks (GitHub) (differs)6 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (ghcr.io/copyleftdev/kalshi-kernel:0.1.1)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 14, secrets among them: 1
Parts of the bundle (differs)212
Licence (differs)MITApache-2.0
Repository (differs)github.com/ellipsis-labs/vulcan-cligithub.com/copyleftdev/kalshi-kernel
Changes in the last 7 days (differs)02
First seen (differs)2026-10-122026-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

vulcan

In its own words, on Claude Code: claude-plugins-community:

Agent and human-friendly CLI for trading Phoenix perpetual futures on Solana.

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

vulcan As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install vulcan@claude-community

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 vulcan asks for

  • VULCAN_WALLET_NAME
  • VULCAN_WALLET_PASSWORD (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: vulcan · What it can do: Kalshi Kernel · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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