Dinero en la Mesa — Perp DEX costs & funding
Dinero en la Mesa: live all-in cost (fees + slippage) and funding on 28 perp DEXs. Free, read-only.
作者提供的说明(英文原文)
Cross-venue Polymarket+Kalshi arbitrage: resolution mismatch, void risk & settlement divergence.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://api.crosswire-api.com/mcp在终端中运行这条命令
claude mcp add --transport http crosswire-polymarket-kalshi-arbitrage https://api.crosswire-api.com/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"crosswire-polymarket-kalshi-arbitrage": {
"url": "https://api.crosswire-api.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"crosswire-polymarket-kalshi-arbitrage": {
"type": "http",
"url": "https://api.crosswire-api.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://api.crosswire-api.com/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
发布者(crosswire-api.com)不是仓库所有者(NicolasDuarte04);可能是其他人代为上架的
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 0 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(0.6.2)于5个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Dinero en la Mesa — Perp DEX costs & funding, CryptoKeyhole, Cloud Wallet by Ekubo
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Dinero en la Mesa: live all-in cost (fees + slippage) and funding on 28 perp DEXs. Free, read-only.
Read-only market and on-chain data for Bitcoin, Ethereum and more; on-chain from our own nodes.
EVM wallet reads, simulation, and transaction execution under user-defined authorization policies.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
https://api.crosswire-api.com/mcp
Generic MCP client config (mcp.json):
{
"mcpServers": { "crosswire": { "url": "https://api.crosswire-api.com/mcp" } } }
Claude Code:
claude mcp add --transport http crosswire https://api.crosswire-api.com/mcp
check_resolution_riskPre-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 from list_covered_events, e.g. "wc26:match:MEX-RSA:2026-06-11:result#home" (#home / #draw / #away selects the outcome leg), ormarket_a + market_b — one Polymarket conditionId (0x… hex) and one Kalshi ticker (e.g. KXWCGAME-26JUN11MEXRSA-MEX), order-insensitive. outcome on 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:
{
"canonical_event_id": "wc26:match:MEX-RSA:2026-06-11:result#home" }
Response (abridged with …):
{
"audit_id": "aud_01KTW2Y7S3Q3JFYJK863FJB66X", "canonical_event_id": "wc26:match:MEX-RSA:2026-06-11:result#home", "leg_a": { "venue": "polymarket", "market_id": "0x4cd77d45…10ff", "outcome": "Yes" }, "leg_b": { "venue": "kalshi", "market_id": "KXWCGAME-26JUN11MEXRSA-MEX", "outcome": "yes" }, "matching_confidence": 0.98, "semantically_fungible": false, "scope_divergence_flag": false, "void_rule_divergence_flag": true, "settlement_source_divergence_flag": true, "settlement_timing_divergence_flag": true, "polymarket_rule_override": "If the game is canceled entirely, with no make-up game, this market will resolve \"No\". …", "kalshi_rule_override": "If the game is cancelled or rescheduled to over two weeks away, the market will resolve to a fair price …", "findings": [ { "code": "void_rule", "severity": "fatal", "detail": "Void conditions differ … A core void asymmetry can void one leg while the other settles.", "affects_fungibility": true }, { "code": "settlement_source", "severity": "warn", "detail": "fifa.com (UMA-adjudicated) vs Kalshi internal …" }, { "code": "settlement_timing", "severity": "warn", "detail": "2h statistics fallback vs unspecified …" } ], "fee_adjusted_true_spread": 0.0009, "snapshot_age_seconds": 61, "execution_verdict": "block", "verdict_reasons": [ "void_rule: Void conditions differ …", "…" ], "ruleset_sha": "…" }
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_eventsFree 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 | Meaning | Agent action |
|---|---|---|
safe | No fatal findings, data fresh. The two contracts settle on the same thing. | Proceed; your stack decides. |
caution | Non-fatal divergence or degraded data (e.g. stale snapshot, thin liquidity, source/timing gaps). | Proceed only if your strategy tolerates the named finding. |
block | A fatal divergence (void-rule asymmetry, scope mismatch, granularity mismatch…) can settle the legs differently. | Do not execute the pair as a hedge. |
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}.
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.
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: nicolasduartejaraba@gmail.com.
Crosswire is an advisory data service. Nothing it returns is financial advice.
MIT — covers this repository (listing metadata and documentation). The Crosswire service itself is proprietary.