mcp-registry/dev.infranode/infranode/transit / alternatives

Live alternatives to mcp-registry/dev.infranode/infranode/transit

The best live alternatives to mcp-registry/dev.infranode/infranode/transit right now are mcp-registry/io.github.pipeworx-io/transit-land/departures_at_stop, mcp-registry/com.gojinko.mcp/jinko/find_ground, mcp-registry/io.github.pipeworx-io/swisstransport/get_connections, mcp-registry/io.github.vbhjckfd/timetable-api-node/get_stops_around_location, mcp-registry/io.github.srivastsh/muni-mcp/muni_departures_by_route_stop — capability-matched and ranked by current reliability. mcp-registry/dev.infranode/infranode/transit itself is currently "healthy".

alternativeserver
mcp-registry/io.github.pipeworx-io/transit-land/departures_at_stopio.github.pipeworx-io/transit-landlive status →
mcp-registry/com.gojinko.mcp/jinko/find_groundcom.gojinko.mcp/jinkolive status →
mcp-registry/io.github.pipeworx-io/swisstransport/get_connectionsio.github.pipeworx-io/swisstransportlive status →
mcp-registry/io.github.vbhjckfd/timetable-api-node/get_stops_around_locationio.github.vbhjckfd/timetable-api-nodelive status →
mcp-registry/io.github.srivastsh/muni-mcp/muni_departures_by_route_stopio.github.srivastsh/muni-mcplive status →
mcp-registry/io.github.vbhjckfd/timetable-api-node/get_stop_realtimeio.github.vbhjckfd/timetable-api-nodelive status →
mcp-registry/io.github.vbhjckfd/timetable-api-node/plan_tripio.github.vbhjckfd/timetable-api-nodelive status →
mcp-registry/io.github.pipeworx-io/swisstransport/get_stationboardio.github.pipeworx-io/swisstransportlive status →
mcp-registry/io.github.andrew-sondgeroth/zipexplore-mcp/get_transit_profileio.github.andrew-sondgeroth/zipexplore-mcplive status →
mcp-registry/io.github.pipeworx-io/swisstransport/search_stationsio.github.pipeworx-io/swisstransportlive status →
mcp-registry/io.github.pipeworx-io/tfl/arrivalsio.github.pipeworx-io/tfllive status →
mcp-registry/io.github.vbhjckfd/timetable-api-node/get_nearby_vehiclesio.github.vbhjckfd/timetable-api-nodelive status →

FAQ

What is the best alternative to mcp-registry/dev.infranode/infranode/transit?

mcp-registry/io.github.pipeworx-io/transit-land/departures_at_stop is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.gojinko.mcp/jinko/find_ground, mcp-registry/io.github.pipeworx-io/swisstransport/get_connections, mcp-registry/io.github.vbhjckfd/timetable-api-node/get_stops_around_location, mcp-registry/io.github.srivastsh/muni-mcp/muni_departures_by_route_stop. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/dev.infranode/infranode/transit down right now?

mcp-registry/dev.infranode/infranode/transit's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fdev.infranode%2Finfranode%2Ftransit.

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%2Fdev.infranode%2Finfranode%2Ftransit or MCP find_alternatives. Check mcp-registry/dev.infranode/infranode/transit's live status: https://glimind.com/tool/mcp-registry/dev.infranode/infranode/transit.