com.crosswire-api/crosswire-polymarket-kalshi-arbitrage

Est-ce que com.crosswire-api/crosswire-polymarket-kalshi-arbitrage est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.crosswire-api/crosswire-polymarket-kalshi-arbitrage » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 2 outils

• check_resolution_risk≈ 1226 tokens

  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.

  Paramètres, retour & exemple (6)

  Paramètres

  • mode · string · optionnel
    'advisory' (default) or 'strict'.
  • api_key · ? · optionnel
    Crosswire API key (cw_…). Optional. Free for the World Cup graph and the first calls/day on metered crypto pairs; beyond that, metered crypto calls draw down this key's prepaid USDC balance (top up via the x402 /v1/credits/topup endpoint).
  • market_a · ? · optionnel
    First leg of the pair to audit (either venue; order does not matter). Provide market_a AND market_b together, or use canonical_event_id instead.
  • market_b · ? · optionnel
    Second leg of the pair to audit (the other venue).
  • notional_usd · ? · optionnel
    Intended position size in USD. Optional; sizes the thin-liquidity check against live top-of-book depth.
  • canonical_event_id · ? · optionnel
    A covered pair id — the outcome-suffixed canonical id. Two namespaces: the metered crypto oracle-divergence inventory (shape 'crypto:btc-above:<date>:strike-<n>#above' — $0.02 USDC per call after 3 free calls/day; the daily pair rolls, so fetch a current id from list_covered_events rather than reusing an old one) and the free World Cup football pairs (shape 'wc26:match:<TEAMS>:<date>:result#home|#draw|#away'; the suffix selects the outcome leg-pair). A bare event id without the suffix is ambiguous and only accepted when market_a + market_b are also given to select the leg. Always get live pair ids from list_covered_events.

  Exemple d'appel

  {"name": "check_resolution_risk", "arguments": {"mode": "texte", "api_key": "texte", "market_a": "texte", "market_b": "texte", "notional_usd": "texte", "canonical_event_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_covered_events≈ 224 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_covered_events", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://api.crosswire-api.com/mcp