Ext Ops Panel
Open dashboard
Comparison

Monte-Neo strategy verifier vs Kalshi Kernel

Monte-Neo strategy verifier is an MCP server published by NeoZorK. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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-18. 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
MarketplaceMonte-Neo strategy verifierKalshi Kernel
Official MCP Registry Listed
Version: 0.53.1
Downloads/month (PyPI): 5 691
Downloads/week (PyPI): 598
Forks (GitHub): 0
Stars (GitHub): 8
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

Monte-Neo strategy verifier vs Kalshi Kernel
FactMonte-Neo strategy verifierKalshi Kernel
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)8 (better)0 (worse)
Forks (GitHub)00
Last release (differs)2026-10-12Not published
Where it runs (differs)On your machine (monte-neo)On your machine (ghcr.io/copyleftdev/kalshi-kernel:0.1.1)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published4, secrets among them: 1
Hooks it runs (differs)1Not published
Parts of the bundle (differs)4Not a bundle
Licence (differs)MITApache-2.0
Repository (differs)github.com/neozork/monte-neogithub.com/copyleftdev/kalshi-kernel
Changes in the last 7 days44
First seen2026-10-112026-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

Monte-Neo strategy verifier

In its own words, on Official MCP Registry:

Verify trading-strategy backtests: look-ahead probes, trading costs, Deflated Sharpe, walk-forward.

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

Monte-Neo strategy verifier As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio monte-neo -- uvx monte-neo mcp

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

The marketplaces of Monte-Neo strategy verifier publish no settings it asks for, so we do not compare settings.

What it can do: Monte-Neo strategy verifier · 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