mcp-registry/io.github.baneado98/freight-pulse/incoterm_responsibility / alternatives

Live alternatives to mcp-registry/io.github.baneado98/freight-pulse/incoterm_responsibility

The best live alternatives to mcp-registry/io.github.baneado98/freight-pulse/incoterm_responsibility right now are mcp-registry/io.github.ipayx-technologies/mcp-fx-audit/compare_fx_sources, mcp-registry/io.github.ipayx-stellar/fx-audit/compare_fx_sources, mcp-registry/io.github.pipeworx-io/kalshi/kalshi_market, mcp-registry/io.github.pipeworx-io/monday/polymarket_kalshi_spread, mcp-registry/io.github.pipeworx-io/monarch-initiative/polymarket_kalshi_spread — capability-matched and ranked by current reliability. mcp-registry/io.github.baneado98/freight-pulse/incoterm_responsibility itself is currently "healthy".

alternative	server
mcp-registry/io.github.ipayx-technologies/mcp-fx-audit/compare_fx_sources	io.github.iPAYX-Technologies/mcp-fx-audit	live status →
mcp-registry/io.github.ipayx-stellar/fx-audit/compare_fx_sources	io.github.Ipayx-stellar/fx-audit	live status →
mcp-registry/io.github.pipeworx-io/kalshi/kalshi_market	io.github.pipeworx-io/kalshi	live status →
mcp-registry/io.github.pipeworx-io/monday/polymarket_kalshi_spread	io.github.pipeworx-io/monday	live status →
mcp-registry/io.github.pipeworx-io/monarch-initiative/polymarket_kalshi_spread	io.github.pipeworx-io/monarch-initiative	live status →
mcp-registry/io.github.pipeworx-io/mercury-number/polymarket_kalshi_spread	io.github.pipeworx-io/mercury-number	live status →
mcp-registry/io.github.pipeworx-io/bored/polymarket_kalshi_spread	io.github.pipeworx-io/bored	live status →
mcp-registry/io.github.pipeworx-io/arcgis-eagan/polymarket_kalshi_spread	io.github.pipeworx-io/arcgis-eagan	live status →
mcp-registry/io.github.pipeworx-io/imgflip/polymarket_kalshi_spread	io.github.pipeworx-io/imgflip	live status →
mcp-registry/io.github.pipeworx-io/hunter/polymarket_kalshi_spread	io.github.pipeworx-io/hunter	live status →
mcp-registry/io.github.pipeworx-io/inspire-hep/polymarket_kalshi_spread	io.github.pipeworx-io/inspire-hep	live status →
mcp-registry/io.github.pipeworx-io/airtable/polymarket_kalshi_spread	io.github.pipeworx-io/airtable	live status →

FAQ

What is the best alternative to mcp-registry/io.github.baneado98/freight-pulse/incoterm_responsibility?

mcp-registry/io.github.ipayx-technologies/mcp-fx-audit/compare_fx_sources is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.ipayx-stellar/fx-audit/compare_fx_sources, mcp-registry/io.github.pipeworx-io/kalshi/kalshi_market, mcp-registry/io.github.pipeworx-io/monday/polymarket_kalshi_spread, mcp-registry/io.github.pipeworx-io/monarch-initiative/polymarket_kalshi_spread. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.baneado98/freight-pulse/incoterm_responsibility down right now?

mcp-registry/io.github.baneado98/freight-pulse/incoterm_responsibility's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.baneado98%2Ffreight-pulse%2Fincoterm_responsibility.

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.baneado98%2Ffreight-pulse%2Fincoterm_responsibility or MCP find_alternatives. Check mcp-registry/io.github.baneado98/freight-pulse/incoterm_responsibility's live status: https://glimind.com/tool/mcp-registry/io.github.baneado98/freight-pulse/incoterm_responsibility.