Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

app.oddsrail/polymarket-kalshi-arbitrage

PYPI · ODDSRAIL

Cross-venue prediction markets for AI agents: Polymarket + Kalshi, costed and attributed

Available components

−15 this week 69 Trust /100

Last scanned (10 hours ago)

Scores higher than 62% of PyPI servers

Deprecated

This server is marked deprecated in the MCP registry. The registry records this reason: renamed to app.oddsrail/polymarket-kalshi-trading.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 57 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 45 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2656 tokens (~68/item across 39 items; 39 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 40 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 20 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 19 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 18 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 16 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.97 → pass security
  • 15 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
    • Stability: 0.97 → pass security
  • 7 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed pypi/oddsrail@0.10.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 57 packages
Packages resolved 57
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 39 exposed · ~2,372 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
builder_stats ~48

Builder attribution stats: the public builder leaderboard, and (if ODDSRAIL_BUILDER_CODE is set) matched trades attributed to this operator's code.

NameTypeReqDescription
time_periodstring––

No output schema declared.

No examples provided.

cancel_all_orders ~41

KILL SWITCH — cancel every resting Polymarket order on the operator account at once. Use when exposure must go to zero fast. Respects dry-run.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

cancel_order ~28

Cancel an open order by id (respects dry-run).

NameTypeReqDescription
order_idstringyes–

No output schema declared.

No examples provided.

closing_soon ~47

Markets closing within N hours on either venue, by volume — where trading activity concentrates.

NameTypeReqDescription
hoursnumber––
limitinteger––
venuesstring––

No output schema declared.

No examples provided.

compare_venues ~112

Find markets that may be the SAME event on both Polymarket and Kalshi. NOT an arbitrage scanner: matches are candidates from title similarity plus a close-date check, and a price difference between two candidates is not profit. Identical wording does not mean identical resolution criteria — read both, and run quote_cost on each leg, before acting.

NameTypeReqDescription
limitinteger––
max_close_days_apartinteger––
min_similaritynumber––
querystringyes–

No output schema declared.

No examples provided.

dispute_risk ~48

PREMIUM SIGNAL — dispute-risk triage. Scores 0-100 how likely a market's resolution gets contested (UMA dispute risk) with transparent reasons.

NameTypeReqDescription
id_or_slugstringyes–

No output schema declared.

No examples provided.

find_markets ~110

Search BOTH Polymarket and Kalshi at once and return one normalised shape per market: venue, market_id (the id that venue's place_order takes), title, yes/no price as probabilities in (0,1), best bid/ask, spread, 24h volume, close time. Use this instead of the per-venue search tools when you do not already know the venue.

NameTypeReqDescription
limitinteger––
querystringyes–
venuesstring––

No output schema declared.

No examples provided.

get_market ~28

Get one market's details by slug (or id).

NameTypeReqDescription
id_or_slugstringyes–

No output schema declared.

No examples provided.

get_orderbook ~35

Get the live orderbook (bids/asks) for a CLOB token id.

NameTypeReqDescription
token_idstringyes–

No output schema declared.

No examples provided.

get_positions ~29

Current positions for a wallet address.

NameTypeReqDescription
addressstringyes–
limitinteger––

No output schema declared.

No examples provided.

kalshi_balance ~21

Kalshi account balance (needs the operator's API key).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

kalshi_cancel_order ~31

Cancel a Kalshi order by id (respects dry-run).

NameTypeReqDescription
order_idstringyes–

No output schema declared.

No examples provided.

kalshi_get_market ~25

Get one Kalshi market by ticker.

NameTypeReqDescription
tickerstringyes–

No output schema declared.

No examples provided.

kalshi_get_orderbook ~67

Kalshi orderbook for a ticker, normalised to a YES-book bid/ask view (Kalshi publishes bid ladders only; asks are derived as 1 - NO bid). Raw ladders included.

NameTypeReqDescription
depthinteger––
tickerstringyes–

No output schema declared.

No examples provided.

kalshi_get_trades ~34

Recent public trades for a Kalshi ticker.

NameTypeReqDescription
limitinteger––
tickerstringyes–

No output schema declared.

No examples provided.

kalshi_open_orders ~29

Kalshi resting orders (needs the operator's API key).

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

kalshi_place_order ~107

Place a Kalshi limit order. State it naturally: outcome yes|no, action buy|sell, price = probability of THAT outcome in (0,1). Translated to Kalshi's YES-book bid/ask internally. DRY-RUN by default.

NameTypeReqDescription
actionstringyes–
countnumberyes–
outcomestringyes–
pricenumberyes–
tickerstringyes–
time_in_forcestring––

No output schema declared.

No examples provided.

kalshi_positions ~27

Kalshi positions (needs the operator's API key).

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

kalshi_search_markets ~75

Search Kalshi markets. Kalshi has no text-search endpoint, so this pages open markets and filters on title/ticker; auto-generated MVE combo shards are excluded. Prices are dollar strings, not cents.

NameTypeReqDescription
limitinteger––
min_volumenumber––
querystring––

No output schema declared.

No examples provided.

merge_positions ~72

Merge matching YES+NO shares back into USDC, GASLESS via the relayer. amount is in shares, or 'max' for the largest balanced amount held. Needs the operator's relayer key. DRY-RUN by default.

NameTypeReqDescription
amountstring––
condition_idstringyes–

No output schema declared.

No examples provided.

my_fills ~35

Recent executions (fills) for the operator wallet — confirms what actually traded, with tx hashes.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

my_positions ~33

The operator's current Polymarket positions (uses the configured wallet; no address needed).

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

open_orders ~16

List the operator wallet's open orders.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

order_status ~44

Status of one Polymarket order: resting, partially filled, filled, or gone. The lifecycle answer an agent needs after place_order.

NameTypeReqDescription
order_idstringyes–

No output schema declared.

No examples provided.

overshoot_signal ~79

PREMIUM SIGNAL — overshoot/fade detector. Analyzes a token's recent price series for fresh panic jumps and reports whether a fade setup is active plus this market's historical reversion tendency.

NameTypeReqDescription
hoursnumber––
lookback_snumber––
thresholdnumber––
token_idstringyes–

No output schema declared.

No examples provided.

paper_positions ~78

Paper-trading portfolio for dry-run: cash, positions at current marks, realized and unrealized P&L, resting paper orders (filled here if the market has crossed them). Dry-run Polymarket orders are papered against the live book automatically. Simulated: no queue, no impact, no fees, so results are an upper bound.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

paper_reset ~45

Reset the paper-trading ledger to its starting bankroll (ODDSRAIL_PAPER_BANKROLL, default 1000 USDC). Deletes simulated fills and positions; touches nothing real.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

place_order ~145

Place a limit order. DRY-RUN by default: returns the order it would post. Real trading needs ODDSRAIL_DRY_RUN=0 and POLYMARKET_PRIVATE_KEY. The operator's builder code is signed into the order. price is the implied probability in (0,1); size is in SHARES (notional = price * size), and the exchange enforces a $1 minimum notional on marketable orders. post_only=True rejects rather than crosses the book.

NameTypeReqDescription
post_onlyboolean––
pricenumberyes–
sidestringyes–
sizenumberyes–
token_idstringyes–

No output schema declared.

No examples provided.

position_size ~93

Fractional-Kelly position size for a binary contract, given your bankroll, the market price, and YOUR fair value estimate. Caps at a fraction of full Kelly and refuses negative-edge bets. Returns its assumptions — subtract quote_cost before trusting the number.

NameTypeReqDescription
bankroll_usdnumberyes–
fair_valuenumberyes–
max_fraction_of_kellynumber––
pricenumberyes–

No output schema declared.

No examples provided.

price_history ~49

Recent price history for a CLOB token id: hours back, at fidelity_minutes resolution.

NameTypeReqDescription
fidelity_minutesinteger––
hoursnumber––
token_idstringyes–

No output schema declared.

No examples provided.

quote_cost ~108

What a given size would ACTUALLY cost, by walking the order book rather than reading the top level. Returns average fill price, slippage vs best, notional, and the levels consumed — plus the venue's fee schedule where it publishes one. Call this before sizing any trade, and on both legs before acting on a cross-venue gap.

NameTypeReqDescription
market_idstringyes–
sidestringyes–
sizenumberyes–
venuestringyes–

No output schema declared.

No examples provided.

redeem_positions ~71

Redeem the winning shares of a RESOLVED market for USDC, GASLESS via the relayer. Pass exactly one of condition_id or market_id. Needs the operator's relayer key. DRY-RUN by default.

NameTypeReqDescription
condition_idstring––
market_idstring––

No output schema declared.

No examples provided.

redeemable_positions ~61

What the operator can turn back into USDC now: redeemable (resolved, winning) positions and mergeable (hold both YES and NO) positions, with the ids the gasless tools take. Uses the configured wallet.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

resolution_criteria ~74

READ BEFORE TRUSTING A PRICE: the full resolution contract for a market — what exactly resolves YES, who resolves it, from which sources. venue is 'polymarket' (pass slug or id) or 'kalshi' (pass ticker).

NameTypeReqDescription
market_idstringyes–
venuestringyes–

No output schema declared.

No examples provided.

search_markets ~55

Search Polymarket markets by text (Gamma public-search under the hood); empty query lists open markets. Returns token ids, prices, metrics, resolution info.

NameTypeReqDescription
limitinteger––
querystring––

No output schema declared.

No examples provided.

server_info ~62

Server status: dry-run state, attribution config, enabled capabilities, venue reachability from this machine, and Polymarket's geoblock verdict for this machine's IP (advisory — not a compliance check). Call this before the first order of a session.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

settlement_audit ~100

Settlement-divergence audit for a cross-venue pair, on LIVE data (no pre-curated pair list). Compares close times, resolution sources, UMA dispute status and market structure, and returns ok / caution / block with reasons. Run this before treating any cross-venue price difference as an edge.

NameTypeReqDescription
kalshi_tickerstringyes–
notional_usdnumber––
polymarket_idstringyes–

No output schema declared.

No examples provided.

split_position ~114

Split USDC collateral into a full YES+NO share set for one market, GASLESS via Polymarket's relayer. amount_usdc is collateral in USDC (e.g. 25). Needs POLYMARKET_RELAYER_API_KEY and POLYMARKET_RELAYER_API_KEY_ADDRESS (polymarket.com -> Settings -> Relayer API keys). DRY-RUN by default. Never falls back to a gas-paying broadcast.

NameTypeReqDescription
amount_usdcnumberyes–
condition_idstringyes–

No output schema declared.

No examples provided.

watch_book ~96

Stream one Polymarket token's realtime market events (book snapshot, price changes, trades) for up to `seconds` (1-60) or `max_events`, then return them. Use after get_orderbook when you need to see the book MOVE before acting; a quiet market may deliver only the initial snapshot.

NameTypeReqDescription
max_eventsinteger––
secondsnumber––
token_idstringyes–

No output schema declared.

No examples provided.

Install

How do I install the app.oddsrail/polymarket-kalshi-arbitrage MCP server?

app.oddsrail/polymarket-kalshi-arbitrage runs locally as a PyPI package, launched with uvx oddsrail. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · oddsrail

# add to Claude Code
claude mcp add app-oddsrail-polymarket-kalshi-arbitrage -- uvx oddsrail
Common questions

What is the app.oddsrail/polymarket-kalshi-arbitrage MCP server?

app.oddsrail/polymarket-kalshi-arbitrage is an MCP server listed in the public MCP registry as app.oddsrail/polymarket-kalshi-arbitrage. Cross-venue prediction markets for AI agents: Polymarket + Kalshi, costed and attributed. This page covers its PyPI package (oddsrail).

Is the app.oddsrail/polymarket-kalshi-arbitrage MCP server safe to use?

app.oddsrail/polymarket-kalshi-arbitrage scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the app.oddsrail/polymarket-kalshi-arbitrage MCP server expose?

app.oddsrail/polymarket-kalshi-arbitrage exposes 39 tools: search_markets, get_market, get_orderbook, price_history, get_positions, and 34 more. Their descriptions and schemas cost roughly 2,372 tokens of context every time the server is loaded.

Is the app.oddsrail/polymarket-kalshi-arbitrage MCP server still maintained?

app.oddsrail/polymarket-kalshi-arbitrage is marked deprecated in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the app.oddsrail/polymarket-kalshi-arbitrage MCP server under?

app.oddsrail/polymarket-kalshi-arbitrage declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the app.oddsrail/polymarket-kalshi-arbitrage MCP server?

VerifyMCP ran 15 checks on app.oddsrail/polymarket-kalshi-arbitrage, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about app.oddsrail/polymarket-kalshi-arbitrage: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.