Crosswire — Polymarket & Kalshi Arbitrage MCP server
com.crosswire-api/crosswire-polymarket-kalshi-arbitragecrosswire-api.comstreamable-httpv0.6.2Scanned
Cross-venue Polymarket+Kalshi arbitrage: resolution mismatch, void risk & settlement divergence.
2 tools: 1 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Crosswire — Polymarket & Kalshi Arbitrage MCP server can do
The Crosswire — Polymarket & Kalshi Arbitrage MCP server is published by crosswire-api.com, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: check_resolution_risk), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 0.6.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Changes things 1Claude Code: ask
check_resolution_riskPre-trade safety check for cross-venue event markets (crypto oracle-divergence pairs, metered; World Cup football, free).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
Only reads 1Show 1 read-only tool
list_covered_eventsFree 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…No findings
Why it is in this group
- The name "list_covered_events" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:36 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.crosswire-api.com/mcp: tools/list returned 2 tools to an anonymous client, including check_resolution_risk (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.6.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http crosswire-polymarket-kalshi-arbitrage https://api.crosswire-api.com/mcpclaude mcp add --transport http crosswire-polymarket-kalshi-arbitrage https://api.crosswire-api.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__crosswire-polymarket-kalshi-arbitrage__list_covered_events"
],
"ask": [
"mcp__crosswire-polymarket-kalshi-arbitrage__check_resolution_risk"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as crosswire-polymarket-kalshi-arbitrage. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.crosswire-api/crosswire-polymarket-kalshi-arbitrage/verify?hash=f3da814dbf7e5898fd295e5ef44b01746d3c55e740c7de55507114574c3f22b9" | jq -e '.changed == false'Pinned hash f3da814dbf7e, from Nov 10, 2026, 13:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.crosswire-api/crosswire-polymarket-kalshi-arbitrage/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.crosswire-api/crosswire-polymarket-kalshi-arbitrage)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:53 UTC.
Crosswire — Polymarket & Kalshi Arbitrage MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Crosswire — Polymarket & Kalshi Arbitrage MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Crosswire — Polymarket & Kalshi Arbitrage MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Crosswire — Polymarket & Kalshi Arbitrage MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Crosswire — Polymarket & Kalshi Arbitrage MCP server have?
- 2 tools: 1 write, 1 read. check_resolution_risk and list_covered_events.
Does the Crosswire — Polymarket & Kalshi Arbitrage MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Crosswire — Polymarket & Kalshi Arbitrage MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Crosswire — Polymarket & Kalshi Arbitrage MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.