mcp-registry/io.github.pipeworx-io/f1/get_schedule / alternatives
mcp-registry/io.github.pipeworx-io/f1/get_scheduleThe best live alternatives to mcp-registry/io.github.pipeworx-io/f1/get_schedule right now are mcp-registry/io.github.pipeworx-io/openf1/get_meetings, mcp-registry/io.github.pipeworx-io/openf1/get_sessions, mcp-registry/com.adbutler/mcp-server/get_schedule, pulsemcp/adbutler/get_schedule, mcp-registry/xyz.spocal/sports/get_competition_schedule — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/f1/get_schedule itself is currently "healthy".
mcp-registry/io.github.pipeworx-io/openf1/get_meetings is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/openf1/get_sessions, mcp-registry/com.adbutler/mcp-server/get_schedule, pulsemcp/adbutler/get_schedule, mcp-registry/xyz.spocal/sports/get_competition_schedule. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.pipeworx-io/f1/get_schedule's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Ff1%2Fget_schedule.
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%2Fio.github.pipeworx-io%2Ff1%2Fget_schedule
or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/f1/get_schedule's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/f1/get_schedule.