mcp-registry/io.github.pipeworx-io/tfl/disruptions / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/tfl/disruptions

The best live alternatives to mcp-registry/io.github.pipeworx-io/tfl/disruptions right now are mcp-registry/com.moltravel/travel/ferryhopper_get_disruptions, mcp-registry/io.github.pipeworx-io/imf-portwatch/recent_disruptions, mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_air_cargo_disruptions, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_congestion_news, mcp-registry/io.github.baneado98/freight-pulse/contingency_plan — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/tfl/disruptions itself is currently "healthy".

alternative	server
mcp-registry/com.moltravel/travel/ferryhopper_get_disruptions	com.moltravel/travel	live status →
mcp-registry/io.github.pipeworx-io/imf-portwatch/recent_disruptions	io.github.pipeworx-io/imf-portwatch	live status →
mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_air_cargo_disruptions	io.github.SupplyMaven-SCR/supply-chain-intelligence	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_congestion_news	io.github.vinaybhosle/shippingrates-mcp-server	live status →
mcp-registry/io.github.baneado98/freight-pulse/contingency_plan	io.github.Baneado98/freight-pulse	live status →
mcp-registry/io.github.pipeworx-io/wmata/bus_incidents	io.github.pipeworx-io/wmata	live status →
mcp-registry/dev.infranode/infranode/transit_departures	dev.infranode/infranode	live status →
mcp-registry/io.github.pipeworx-io/data-gov-sg/traffic_incidents	io.github.pipeworx-io/data-gov-sg	live status →
mcp-registry/io.github.baneado98/freight-pulse/get_port_intel	io.github.Baneado98/freight-pulse	live status →
mcp-registry/dev.infranode/infranode/transit	dev.infranode/infranode	live status →
mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/supply_chain_disruption_alerts	io.github.SupplyMaven-SCR/supply-chain-intelligence	live status →
mcp-registry/io.github.lxxmng/ocean-schedules/transit_time	io.github.lxxmng/ocean-schedules	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/tfl/disruptions?

mcp-registry/com.moltravel/travel/ferryhopper_get_disruptions is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/imf-portwatch/recent_disruptions, mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_air_cargo_disruptions, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_congestion_news, mcp-registry/io.github.baneado98/freight-pulse/contingency_plan. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/tfl/disruptions down right now?

mcp-registry/io.github.pipeworx-io/tfl/disruptions's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Ftfl%2Fdisruptions.

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.pipeworx-io%2Ftfl%2Fdisruptions or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/tfl/disruptions's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/tfl/disruptions.