mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_port_congestion_trends / alternatives

Live alternatives to mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_port_congestion_trends

The best live alternatives to mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_port_congestion_trends right now are mcp-registry/io.github.pipeworx-io/opensky/pipeworx_trending, mcp-registry/io.github.pipeworx-io/horizons-nasa/pipeworx_trending, mcp-registry/io.github.pipeworx-io/arcgis-roanoke/pipeworx_trending, mcp-registry/io.github.pipeworx-io/mathjs/pipeworx_trending, mcp-registry/io.github.pipeworx-io/odds-api/pipeworx_trending — capability-matched and ranked by current reliability. mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_port_congestion_trends itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/opensky/pipeworx_trending	io.github.pipeworx-io/opensky	live status →
mcp-registry/io.github.pipeworx-io/horizons-nasa/pipeworx_trending	io.github.pipeworx-io/horizons-nasa	live status →
mcp-registry/io.github.pipeworx-io/arcgis-roanoke/pipeworx_trending	io.github.pipeworx-io/arcgis-roanoke	live status →
mcp-registry/io.github.pipeworx-io/mathjs/pipeworx_trending	io.github.pipeworx-io/mathjs	live status →
mcp-registry/io.github.pipeworx-io/odds-api/pipeworx_trending	io.github.pipeworx-io/odds-api	live status →
mcp-registry/io.github.pipeworx-io/intact/pipeworx_trending	io.github.pipeworx-io/intact	live status →
mcp-registry/io.github.pipeworx-io/temperature-random/pipeworx_trending	io.github.pipeworx-io/temperature-random	live status →
mcp-registry/io.github.pipeworx-io/arcgis-peachtreecorners/pipeworx_trending	io.github.pipeworx-io/arcgis-peachtreecorners	live status →
mcp-registry/io.github.pipeworx-io/worldbank/pipeworx_trending	io.github.pipeworx-io/worldbank	live status →
mcp-registry/io.github.pipeworx-io/the-committee/pipeworx_trending	io.github.pipeworx-io/the-committee	live status →
mcp-registry/io.github.pipeworx-io/bnm-my/pipeworx_trending	io.github.pipeworx-io/bnm-my	live status →
mcp-registry/io.github.pipeworx-io/plos/pipeworx_trending	io.github.pipeworx-io/plos	live status →

FAQ

What is the best alternative to mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_port_congestion_trends?

mcp-registry/io.github.pipeworx-io/opensky/pipeworx_trending is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/horizons-nasa/pipeworx_trending, mcp-registry/io.github.pipeworx-io/arcgis-roanoke/pipeworx_trending, mcp-registry/io.github.pipeworx-io/mathjs/pipeworx_trending, mcp-registry/io.github.pipeworx-io/odds-api/pipeworx_trending. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_port_congestion_trends down right now?

mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_port_congestion_trends's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.supplymaven-scr%2Fsupply-chain-intelligence%2Fget_port_congestion_trends.

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.supplymaven-scr%2Fsupply-chain-intelligence%2Fget_port_congestion_trends or MCP find_alternatives. Check mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_port_congestion_trends's live status: https://glimind.com/tool/mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_port_congestion_trends.