mcp server
Crosswire — Polymarket & Kalshi Arbitrage
Cross-venue Polymarket+Kalshi arbitrage: resolution mismatch, void risk & settlement divergence.
Description as published by the maintainer. Source
- version 0.6.2
- active
- retrieval
active — Most recent push to the repository was 2026-06-21. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
2 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
check_resolution_risk(mode, api_key, market_a, market_b, notional_usd, canonical_event_id)- Pre-trade safety check for cross-venue event markets (crypto oracle-divergence pairs, metered; World Cup football, free). Flags resolution mismatches, void-rule divergence, scope differences (e.g. 90-minute vs extra-time; matched vs differing strike), settlement-source and -timing gaps, stale data, and thin liquidity between the two Polymarket and Kalshi legs BEFORE you execute both. 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 live pair id from list_covered_events — the metered 'crypto:' inventory rolls daily, so fetch a current id there rather than reusing an old one; the free 'wc26:' World Cup pairs are stable) OR market_a + market_b (one Polymarket conditionId + one Kalshi ticker, order-insensitive). If the pair is not covered, returns a non-error coverage reply (covered: false) naming the covered inventories (free World Cup football + metered crypto pairs) and the coverage cutoff instead of an FSAO.
list_covered_events- Free discovery of everything check_resolution_risk can audit across both inventories — the free World Cup football pairs and the metered crypto oracle-divergence pairs (the 'crypto:' namespace is the paid surface: $0.02 USDC per call after 3 free calls/day). Returns the covered canonical events, their per-outcome pair ids (…#home / #draw / #away for football), 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. Use a returned pair_id (or a pair's two market ids) as input to check_resolution_risk.
Last successful function declaration observed on . Source: https://api.crosswire-api.com/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://api.crosswire-api.com/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-06-21 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.6.2 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-21 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-06-21 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub | |
| mcp tools declared | 2 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | api.crosswire-api.com | |
| mcp endpoint status | ok | The server listed 2 functions when asked. | as of probe | api.crosswire-api.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json