Skip to main content
Glama
f1verse MCP Server

f1verse MCP Server

by jinsim

Related Servers

Alternatives to f1verse MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query real-time and historical Formula 1 data through the OpenF1 API, providing tools for driver info, lap times, telemetry, race events, and more.
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      Enables Claude to answer Formula 1 questions using real public data: race, sprint and qualifying results back to 1950, lap and sector times, 4 Hz car telemetry, tyre stints, pit stops and undercut strategy, plus locally drawn speed-trace and gear-shift plots. Also covers live session timing — positions, gaps, tyres, flags and weather — through 77 read-only tools that need no account, login or API key.
      77
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to query Formula 1 sessions, laps, telemetry, stints, pit stops, positions, weather, race control and championship data from the OpenF1 API (2023 onwards), plus composite tools for race summaries, tyre strategies and multi-driver fastest-lap comparisons. It is read-only, caches and throttles requests, and samples or summarizes oversized results so large telemetry payloads stay manageable for the model.
      20
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides comprehensive Formula 1 data and analytics for Claude Desktop, including race results, telemetry, standings, and strategy insights through 36+ tools.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables Formula 1 data analysis through natural language, providing tools like track dominance, lap time analysis, and team performance comparisons.
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      Exposes Formula 1 historical data (race results, qualifying, pit stops, and championship standings) as callable tools for LLMs via the Jolpica-F1 API.
      -

    TDQS

    B3.4/5.0

    Scored across 26 tools

    Disambiguation3/5

    Descriptions carefully carve out boundaries, but several clusters overlap heavily: f1_race_story aggregates results, running order, timeline and stints that f1_session_results, f1_running_order and f1_race_events also expose. Likewise f1_race_events vs f1_turning_points, and f1_circuit_profile vs f1_circuit_survey vs f1_circuit_history, require reading long descriptions to choose correctly. The guidance is good, but an agent can still reasonably hesitate among multiple 'what happened' or 'circuit' tools.

    Naming Consistency4/5

    Every name uses the same f1_ prefix and snake_case, and follows a predictable f1_<domain>_<object> style. The names are mostly noun phrases rather than verb_noun actions, but the convention is consistent throughout with only minor semantic variation (e.g. f1_closest_titles, f1_season_shape).

    Tool Count3/5

    At 26 tools the surface is heavy, well above the comfortable 3-15 range. The breadth of F1 analysis, history and circuit data justifies many of them, but some analytics variants could be consolidated or exposed as options on fewer tools. It is borderline rather than clearly excessive.

    Completeness4/5

    Coverage is unusually broad: live/settled sessions, standings, race narratives, tyre and pace analysis, history, circuits and championship projections are all represented. Minor gaps remain around general driver/team directories, a full season calendar, and some race-control/penalty information beyond deleted laps, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues