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

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

The best live alternatives to mcp-registry/io.github.baneado98/freight-pulse/procurement_strategy right now are mcp-registry/io.github.ipayx-stellar/fx-audit/compare_fx_sources, mcp-registry/io.github.ipayx-technologies/mcp-fx-audit/compare_fx_sources, mcp-registry/io.github.pipeworx-io/wikimedia-rest/polymarket_edges, mcp-registry/io.github.pipeworx-io/data-wa/polymarket_edges, mcp-registry/io.github.pipeworx-io/schrodingers-boolean/polymarket_edges — capability-matched and ranked by current reliability. mcp-registry/io.github.baneado98/freight-pulse/procurement_strategy itself is currently "healthy".

alternative	server
mcp-registry/io.github.ipayx-stellar/fx-audit/compare_fx_sources	io.github.Ipayx-stellar/fx-audit	live status →
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.pipeworx-io/wikimedia-rest/polymarket_edges	io.github.pipeworx-io/wikimedia-rest	live status →
mcp-registry/io.github.pipeworx-io/data-wa/polymarket_edges	io.github.pipeworx-io/data-wa	live status →
mcp-registry/io.github.pipeworx-io/schrodingers-boolean/polymarket_edges	io.github.pipeworx-io/schrodingers-boolean	live status →
mcp-registry/io.github.pipeworx-io/outlook-mail/polymarket_edges	io.github.pipeworx-io/outlook-mail	live status →
mcp-registry/io.github.pipeworx-io/okx/polymarket_edges	io.github.pipeworx-io/okx	live status →
mcp-registry/io.github.pipeworx-io/mychem/polymarket_edges	io.github.pipeworx-io/mychem	live status →
mcp-registry/io.github.pipeworx-io/usgs-earthquakes/polymarket_edges	io.github.pipeworx-io/usgs-earthquakes	live status →
mcp-registry/io.github.pipeworx-io/waqi/polymarket_edges	io.github.pipeworx-io/waqi	live status →
mcp-registry/io.github.pipeworx-io/urlhaus/polymarket_edges	io.github.pipeworx-io/urlhaus	live status →
mcp-registry/io.github.pipeworx-io/numbersapi/polymarket_edges	io.github.pipeworx-io/numbersapi	live status →

FAQ

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

mcp-registry/io.github.ipayx-stellar/fx-audit/compare_fx_sources is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.ipayx-technologies/mcp-fx-audit/compare_fx_sources, mcp-registry/io.github.pipeworx-io/wikimedia-rest/polymarket_edges, mcp-registry/io.github.pipeworx-io/data-wa/polymarket_edges, mcp-registry/io.github.pipeworx-io/schrodingers-boolean/polymarket_edges. Glimind ranks alternatives by semantic similarity and live health.

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

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

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