
Crosswire — Polymarket & Kalshi Arbitrage
com.crosswire-apiv0.6.2Updated Sep 29, 2026
Cross-venue Polymarket+Kalshi arbitrage: resolution mismatch, void risk & settlement divergence.
Installation
In SourceWeft
- Open Crosswire — Polymarket & Kalshi Arbitrage in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"crosswire-polymarket-kalshi-arbitrage": {
"type": "http",
"url": "https://api.crosswire-api.com/mcp"
}
}
}README
Crosswire — MCP server
Pre-trade resolution-risk firewall for cross-venue prediction-market arbitrage. Before executing a two-leg Polymarket + Kalshi position, Crosswire flags resolution mismatch, void risk, and settlement divergence — void-rule asymmetry, settlement-scope differences (90-minute vs extra-time), settlement-source and -timing gaps, stale data, and thin liquidity between Polymarket and Kalshi FIFA World Cup 2026 markets — so automated trading agents don't get blown up by markets that look identical but settle differently. Verdict: safe / caution / block.
It does not predict outcomes and it does not execute trades. It answers one question: if I buy this contract on one venue and sell its twin on the other, do they actually settle on the same thing? When they don't, it names the exact clause that breaks the hedge.
Remote MCP endpoint
- Transport: streamable HTTP
- The MCP tools are free — no API key, no signup
- Website: crosswire-api.com · Status & track record: api.crosswire-api.com
Connect
Generic MCP client config (mcp.json):
Claude Code:
Tools
check_resolution_risk
Pre-trade safety check for a cross-venue pair. Returns a machine-readable verdict —
execution_verdict: safe / caution / block — inside a full Fungibility & Settlement Audit
Object (FSAO) with structured findings, top-level divergence flags, venue rule overrides,
fee-adjusted spread, and verdict reasons.
Identify the pair by either:
canonical_event_id— a pair id fromlist_covered_events, e.g."wc26:match:MEX-RSA:2026-06-11:result#home"(#home/#draw/#awayselects the outcome leg), ormarket_a+market_b— one PolymarketconditionId(0x…hex) and one Kalshi ticker (e.g.KXWCGAME-26JUN11MEXRSA-MEX), order-insensitive.outcomeon a ref is optional — matching uses only(venue, market_id).
Optional: notional_usd (enables the thin-liquidity check at your trade size).
If the pair is not covered, the tool returns a non-error coverage reply (covered: false)
naming the covered matches and the coverage cutoff instead of an FSAO.
Example — real production audit (World Cup opener, Mexico vs South Africa, home leg):
Request:
Response (abridged with …):
That block is the product working as intended: a canceled match pays the Polymarket leg
$0 while Kalshi resolves the same position to "a fair price" — the hedge breaks exactly when
you need it.
list_covered_events
Free discovery of everything check_resolution_risk can audit: the covered canonical events,
their per-outcome pair ids (…#home / #draw / #away), the Polymarket conditionIds and
Kalshi tickers with outcome labels for each pair, match dates, the frozen ruleset_sha
pinning the identity graph, the coverage kickoff cutoff, and snapshot freshness. Takes no
arguments. Use a returned pair_id (or a pair's two market ids) as input to
check_resolution_risk.
Verdict semantics
Every FSAO carries the findings that produced the verdict — the audit is explainable,
append-only logged server-side, and reproducible from
{ruleset_sha, snapshot_ts, canonical_event_id}.
Coverage
FIFA World Cup 2026 match markets listed on both Polymarket and Kalshi, expanding in batches
throughout the tournament. Current coverage is always live — query list_covered_events,
or /v1/events and
/v1/health on the REST API. Listings here are
intentionally coverage-generic; the endpoint is the source of truth.
Pricing & keys
The MCP tools are free at launch — no key. The keyed REST API
(POST /v1/audit, same FSAO) issues free opening-weekend keys by mail:
[email protected].
What we never do
- No outcome prediction. No model probabilities are exposed.
- No execution. No order routing or placement. The gate returns a verdict; your stack decides.
- No custody. No customer keys, funds, or settlement.
- No strategy harvesting. The API sees only the two market references being audited and an optional notional.
Crosswire is an advisory data service. Nothing it returns is financial advice.
License
MIT — covers this repository (listing metadata and documentation). The Crosswire service itself is proprietary.
Source: README.md at commit 8dee28f
Tools
0Version history
1- v0.6.2LatestSep 16, 2026