Backtest360 vs Kalshi Kernel
Backtest360 is an MCP server published by backtest360.com. 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: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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 |  Backtest360 |  Kalshi Kernel |
|---|---|---|
| Official MCP Registry | Listed Version: 0.5.0 Downloads/month (PyPI): 278 Downloads/week (PyPI): 38 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
| Fact | Backtest360 | Kalshi Kernel |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.backtest360.com/mcp) | On your machine (ghcr.io/copyleftdev/kalshi-kernel:0.1.1) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 4, secrets among them: 1 |
| Parts of the bundle (differs) | Not a bundle | 2 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/backtest360/backtest360-mcp | github.com/copyleftdev/kalshi-kernel |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 29 h ago, requires a key | no remote endpoint we check |
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
Backtest360
MCP server exposing the Backtest360 engine API as tools for AI agents.
Kalshi Kernel
Unofficial safety-focused MCP server for Kalshi market data and explicitly authorized trading
How to run each
Backtest360 As a remote MCP server
claude mcp add --transport http backtest360 https://mcp.backtest360.com/mcp --header "X-API-Key: <YOUR_X_API_KEY>"Requires: BACKTEST360_API_KEY (secret), X-API-Key header
Kalshi Kernel As a local MCP server: Docker image
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.1Requires: KALSHI_API_KEY_ID (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Backtest360 has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Backtest360 asks for
BACKTEST360_API_KEY (secret)
Only Kalshi Kernel asks for
KALSHI_API_KEY_ID (secret)KALSHI_KERNEL_MODEKALSHI_LIVE_TRADING_ACKKALSHI_PRIVATE_KEY_PATH
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Backtest360 · 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.