Skip to main content
Glama
rakeshgangwar

Formula One MCP Server

Related Servers

Alternatives to Formula One MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time and historical Formula 1 racing data through the Model Context Protocol, offering access to timing data, driver stats, race results, telemetry, and more.
      15
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that provides comprehensive Formula One racing data, enabling access to event schedules, driver information, telemetry data, race results, and performance analytics through natural language queries.
      8
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time access to football (soccer) data including fixtures, standings, teams, players, transfers, and injuries through the API-Football service via the Model Context Protocol.
      3
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides easy access to Formula 1 data including championship standings, event info, season calendars, track visualizations, session results, and driver/constructor info via FastF1 and OpenF1 API.
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables access to Formula 1 data from the openF1.org API, including driver information, race results, lap times, telemetry, pit stops, weather conditions, and live position data across multiple seasons.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides Formula 1 data via the Ergast API, enabling users to check current standings, get race results, view the season schedule, and look up driver profiles.
      1 npm
      MIT

    TDQS

    B3.4/5.0

    Scored across 8 tools

    Disambiguation4/5

    Mostly distinct: get_driver_info is reference data, get_session_results is outcomes, and get_telemetry focuses on lap data. However, compare_drivers and analyze_driver_performance both deal with performance analysis and could be confused in some agent workflows.

    Naming Consistency4/5

    Six tools follow a clear get_<noun> pattern, while compare_drivers and analyze_driver_performance use verb_noun instead. This is a minor deviation but the verbs are meaningful and there is no mixed casing or chaotic style.

    Tool Count5/5

    Eight tools is a well-scoped size for an F1 data server, covering schedules, events, sessions, standings, driver information, and analysis without excessive redundancy.

    Completeness4/5

    The set covers core read-only F1 workflows: calendar, event info, session results, standings, driver details, telemetry, and performance analysis. It lacks constructor/team-specific tools and some historical depth, but those are not critical gaps for a typical F1 data agent.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues