mcp-registry/com.proflightsearch/airport-delays/airport.get_delay_status / alternatives
mcp-registry/com.proflightsearch/airport-delays/airport.get_delay_statusThe best live alternatives to mcp-registry/com.proflightsearch/airport-delays/airport.get_delay_status right now are mcp-registry/ai.dynamicfeed/dynamic-feed/airport_delays, mcp-registry/io.github.pipeworx-io/airports/get_airport, mcp-registry/io.github.pipeworx-io/faa-delays/all_delays, mcp-registry/org.memoryapi/flight/get_airport_info, mcp-registry/io.github.soapyred/freightutils/airport_lookup — capability-matched and ranked by current reliability. mcp-registry/com.proflightsearch/airport-delays/airport.get_delay_status itself is currently "healthy".
mcp-registry/ai.dynamicfeed/dynamic-feed/airport_delays is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/airports/get_airport, mcp-registry/io.github.pipeworx-io/faa-delays/all_delays, mcp-registry/org.memoryapi/flight/get_airport_info, mcp-registry/io.github.soapyred/freightutils/airport_lookup. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/com.proflightsearch/airport-delays/airport.get_delay_status's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcom.proflightsearch%2Fairport-delays%2Fairport.get_delay_status.
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.
Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fcom.proflightsearch%2Fairport-delays%2Fairport.get_delay_status
or MCP find_alternatives. Check mcp-registry/com.proflightsearch/airport-delays/airport.get_delay_status's live status: https://glimind.com/tool/mcp-registry/com.proflightsearch/airport-delays/airport.get_delay_status.