Ext Ops Panel
Open dashboard
Comparison

Kalshi Kernel vs io.github.polyparlay/hypelens-agent-rail

Kalshi Kernel is an MCP server published by copyleftdev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.polyparlay/hypelens-agent-rail is an MCP server published by polyparlay. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
MarketplaceKalshi Kernelio.github.polyparlay/hypelens-agent-rail
Official MCP Registry Listed
Version: 0.1.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.16
Downloads/month (npm): 609
Downloads/week (npm): 85
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

Kalshi Kernel vs io.github.polyparlay/hypelens-agent-rail
FactKalshi Kernelio.github.polyparlay/hypelens-agent-rail
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (ghcr.io/copyleftdev/kalshi-kernel:0.1.1)On your machine (@hypelens/hypelens-agent-rail)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for4, secrets among them: 14, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/copyleftdev/kalshi-kernelgithub.com/polyparlay/hypelens
Changes in the last 7 days (differs)40
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

Kalshi Kernel

In its own words, on Official MCP Registry:

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

io.github.polyparlay/hypelens-agent-rail

In its own words, on Official MCP Registry:

Place/cancel/close HL perps via MCP. Agent wallet once, 1bp fills, no sub.

How to run each

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)

io.github.polyparlay/hypelens-agent-rail As a local MCP server: npm package

Claude Code
claude mcp add --env "HYPELENS_AGENT_PK=<YOUR_HYPELENS_AGENT_PK>" --transport stdio hypelens-agent-rail -- npx -y @hypelens/hypelens-agent-rail

Requires: HYPELENS_AGENT_PK (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 Kalshi Kernel asks for

  • KALSHI_API_KEY_ID (secret)
  • KALSHI_KERNEL_MODE
  • KALSHI_LIVE_TRADING_ACK
  • KALSHI_PRIVATE_KEY_PATH

Only io.github.polyparlay/hypelens-agent-rail asks for

  • HYPELENS_AGENT_PK (secret)
  • HYPELENS_FEED_FILE
  • HYPELENS_FEED_URL
  • HYPELENS_NET

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

What it can do: Kalshi Kernel · What it can do: io.github.polyparlay/hypelens-agent-rail · 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