mcp-registry/io.github.pipeworx-io/edmtrain/locations / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/edmtrain/locations

The best live alternatives to mcp-registry/io.github.pipeworx-io/edmtrain/locations right now are mcp-registry/io.github.pipeworx-io/dostuff/metros, mcp-registry/io.github.localprodev/local-services/list_cities, mcp-registry/com.eventmatey.mcp/event-discovery/search_events_nearby, mcp-registry/com.eveoy/mcp/list_metros, pulsemcp/19hz-events/events — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/edmtrain/locations itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/dostuff/metros	io.github.pipeworx-io/dostuff	live status →
mcp-registry/io.github.localprodev/local-services/list_cities	io.github.LocalProDev/local-services	live status →
mcp-registry/com.eventmatey.mcp/event-discovery/search_events_nearby	com.eventmatey.mcp/event-discovery	live status →
mcp-registry/com.eveoy/mcp/list_metros	com.eveoy/mcp	live status →
pulsemcp/19hz-events/events	19hz Events	live status →
mcp-registry/io.github.pipeworx-io/19hz/events	io.github.pipeworx-io/19hz	live status →
mcp-registry/io.github.pipeworx-io/wmata/rail_lines	io.github.pipeworx-io/wmata	live status →
mcp-registry/io.github.pipeworx-io/ticketmaster/venue_search	io.github.pipeworx-io/ticketmaster	live status →
mcp-registry/co.tempguru/event-staffing/get_cities	co.tempguru/event-staffing	live status →
mcp-registry/io.github.pipeworx-io/ticketmaster/event_search	io.github.pipeworx-io/ticketmaster	live status →
mcp-registry/ai.autonomad/travel/search_events	ai.autonomad/travel	live status →
mcp-registry/io.github.himanshusaleria/events-mcp/list_cities	io.github.himanshusaleria/events-mcp	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/edmtrain/locations?

mcp-registry/io.github.pipeworx-io/dostuff/metros is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.localprodev/local-services/list_cities, mcp-registry/com.eventmatey.mcp/event-discovery/search_events_nearby, mcp-registry/com.eveoy/mcp/list_metros, pulsemcp/19hz-events/events. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/edmtrain/locations down right now?

mcp-registry/io.github.pipeworx-io/edmtrain/locations's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fedmtrain%2Flocations.

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%2Fedmtrain%2Flocations or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/edmtrain/locations's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/edmtrain/locations.