mcp-registry/io.github.digitalweb33333-creator/x402-endpoints/crypto_dex_cex_spread / alternatives

Live alternatives to mcp-registry/io.github.digitalweb33333-creator/x402-endpoints/crypto_dex_cex_spread

The best live alternatives to mcp-registry/io.github.digitalweb33333-creator/x402-endpoints/crypto_dex_cex_spread right now are mcp-registry/io.github.pipeworx-io/vies-eu/polymarket_kalshi_spread, mcp-registry/io.github.pipeworx-io/datos-ar/polymarket_kalshi_spread, mcp-registry/io.github.pipeworx-io/data-santaclara/polymarket_kalshi_spread, mcp-registry/io.github.pipeworx-io/data-nola/polymarket_kalshi_spread, mcp-registry/io.github.pipeworx-io/data-gr/polymarket_kalshi_spread — capability-matched and ranked by current reliability. mcp-registry/io.github.digitalweb33333-creator/x402-endpoints/crypto_dex_cex_spread itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/vies-eu/polymarket_kalshi_spread	io.github.pipeworx-io/vies-eu	live status →
mcp-registry/io.github.pipeworx-io/datos-ar/polymarket_kalshi_spread	io.github.pipeworx-io/datos-ar	live status →
mcp-registry/io.github.pipeworx-io/data-santaclara/polymarket_kalshi_spread	io.github.pipeworx-io/data-santaclara	live status →
mcp-registry/io.github.pipeworx-io/data-nola/polymarket_kalshi_spread	io.github.pipeworx-io/data-nola	live status →
mcp-registry/io.github.pipeworx-io/data-gr/polymarket_kalshi_spread	io.github.pipeworx-io/data-gr	live status →
mcp-registry/io.github.pipeworx-io/nsf-awards/polymarket_kalshi_spread	io.github.pipeworx-io/nsf-awards	live status →
mcp-registry/io.github.pipeworx-io/mitre-attck/polymarket_kalshi_spread	io.github.pipeworx-io/mitre-attck	live status →
mcp-registry/io.github.pipeworx-io/arcgis-puyallup/polymarket_kalshi_spread	io.github.pipeworx-io/arcgis-puyallup	live status →
mcp-registry/io.github.pipeworx-io/usaspending/polymarket_kalshi_spread	io.github.pipeworx-io/usaspending	live status →
mcp-registry/io.github.pipeworx-io/trivia/polymarket_kalshi_spread	io.github.pipeworx-io/trivia	live status →
mcp-registry/io.github.pipeworx-io/the-graph/polymarket_kalshi_spread	io.github.pipeworx-io/the-graph	live status →
mcp-registry/io.github.pipeworx-io/legislation-uk/polymarket_kalshi_spread	io.github.pipeworx-io/legislation-uk	live status →

FAQ

What is the best alternative to mcp-registry/io.github.digitalweb33333-creator/x402-endpoints/crypto_dex_cex_spread?

mcp-registry/io.github.pipeworx-io/vies-eu/polymarket_kalshi_spread is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/datos-ar/polymarket_kalshi_spread, mcp-registry/io.github.pipeworx-io/data-santaclara/polymarket_kalshi_spread, mcp-registry/io.github.pipeworx-io/data-nola/polymarket_kalshi_spread, mcp-registry/io.github.pipeworx-io/data-gr/polymarket_kalshi_spread. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.digitalweb33333-creator/x402-endpoints/crypto_dex_cex_spread down right now?

mcp-registry/io.github.digitalweb33333-creator/x402-endpoints/crypto_dex_cex_spread's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.digitalweb33333-creator%2Fx402-endpoints%2Fcrypto_dex_cex_spread.

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%2Fio.github.digitalweb33333-creator%2Fx402-endpoints%2Fcrypto_dex_cex_spread or MCP find_alternatives. Check mcp-registry/io.github.digitalweb33333-creator/x402-endpoints/crypto_dex_cex_spread's live status: https://glimind.com/tool/mcp-registry/io.github.digitalweb33333-creator/x402-endpoints/crypto_dex_cex_spread.