mcp-registry/com.crosswire-api/crosswire-polymarket-kalshi-arbitrage/list_covered_events / alternatives

Live alternatives to mcp-registry/com.crosswire-api/crosswire-polymarket-kalshi-arbitrage/list_covered_events

The best live alternatives to mcp-registry/com.crosswire-api/crosswire-polymarket-kalshi-arbitrage/list_covered_events right now are mcp-registry/io.github.pipeworx-io/market-spread/compare_topic, mcp-registry/io.github.pipeworx-io/ons-uk/polymarket_kalshi_spread, mcp-registry/io.github.pipeworx-io/19hz/polymarket_kalshi_spread, mcp-registry/io.github.pipeworx-io/intercom/polymarket_kalshi_spread, mcp-registry/io.github.pipeworx-io/hagstofa-is/polymarket_kalshi_spread — capability-matched and ranked by current reliability. mcp-registry/com.crosswire-api/crosswire-polymarket-kalshi-arbitrage/list_covered_events itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/market-spread/compare_topic	io.github.pipeworx-io/market-spread	live status →
mcp-registry/io.github.pipeworx-io/ons-uk/polymarket_kalshi_spread	io.github.pipeworx-io/ons-uk	live status →
mcp-registry/io.github.pipeworx-io/19hz/polymarket_kalshi_spread	io.github.pipeworx-io/19hz	live status →
mcp-registry/io.github.pipeworx-io/intercom/polymarket_kalshi_spread	io.github.pipeworx-io/intercom	live status →
mcp-registry/io.github.pipeworx-io/hagstofa-is/polymarket_kalshi_spread	io.github.pipeworx-io/hagstofa-is	live status →
mcp-registry/io.github.pipeworx-io/cdc/polymarket_kalshi_spread	io.github.pipeworx-io/cdc	live status →
mcp-registry/io.github.pipeworx-io/opentopodata/polymarket_kalshi_spread	io.github.pipeworx-io/opentopodata	live status →
mcp-registry/io.github.pipeworx-io/greenhouse/polymarket_kalshi_spread	io.github.pipeworx-io/greenhouse	live status →
mcp-registry/io.github.pipeworx-io/climate-feeds/polymarket_kalshi_spread	io.github.pipeworx-io/climate-feeds	live status →
mcp-registry/io.github.pipeworx-io/ip-api/polymarket_kalshi_spread	io.github.pipeworx-io/ip-api	live status →
mcp-registry/io.github.pipeworx-io/census-trade/polymarket_kalshi_spread	io.github.pipeworx-io/census-trade	live status →
mcp-registry/io.github.pipeworx-io/arcgis-adamscounty/polymarket_kalshi_spread	io.github.pipeworx-io/arcgis-adamscounty	live status →

FAQ

What is the best alternative to mcp-registry/com.crosswire-api/crosswire-polymarket-kalshi-arbitrage/list_covered_events?

mcp-registry/io.github.pipeworx-io/market-spread/compare_topic is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/ons-uk/polymarket_kalshi_spread, mcp-registry/io.github.pipeworx-io/19hz/polymarket_kalshi_spread, mcp-registry/io.github.pipeworx-io/intercom/polymarket_kalshi_spread, mcp-registry/io.github.pipeworx-io/hagstofa-is/polymarket_kalshi_spread. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/com.crosswire-api/crosswire-polymarket-kalshi-arbitrage/list_covered_events down right now?

mcp-registry/com.crosswire-api/crosswire-polymarket-kalshi-arbitrage/list_covered_events's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcom.crosswire-api%2Fcrosswire-polymarket-kalshi-arbitrage%2Flist_covered_events.

How does Glimind pick alternatives?

By semantic capability match (what the tool does) filtered to tools that are healthy right now — from cross-ecosystem real usage. Neutral: Glimind sells no tools.

For agents

Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fcom.crosswire-api%2Fcrosswire-polymarket-kalshi-arbitrage%2Flist_covered_events or MCP find_alternatives. Check mcp-registry/com.crosswire-api/crosswire-polymarket-kalshi-arbitrage/list_covered_events's live status: https://glimind.com/tool/mcp-registry/com.crosswire-api/crosswire-polymarket-kalshi-arbitrage/list_covered_events.