Public · Read-only · No API key

F1 MCP server

Ask your AI assistant about Formula 1 lap times, tyres, race control and who is catching whom.

fastcarmaps connects compatible AI clients to live timing and recorded session data from Formula 1's own feeds, using the Model Context Protocol (MCP).

Connect your assistant View the tools ↓

Connect

Use an AI client that supports remote MCP servers.

Server URL: https://fastcarmaps.com/mcp
Transport: Streamable HTTP
Authentication: None

Add a remote MCP server in your client.
Paste the server URL above and select no authentication.
Load the tools, then ask which sessions are available.

No F1 account or token is needed. The server URL is for your MCP client; it is not a webpage.

Try asking

“When will George catch Lando at their recent pace?”
“Who set the fastest lap and sectors in Baku Practice 2?”
“What did race control announce during the red flag?”
“Which tyres did Leclerc use, and how old were they?”

Your assistant chooses the tools and explains the results. For historical questions, specify a recorded session or ask what is available first.

Eight tools

Sessions

list_sessions

Find recorded sessions by year, circuit or session name.

Results

get_session

Get the classification, best laps and sectors, weather and track status.

Live timing

get_live_timing

Read the latest running order, gaps, tyres and feed freshness.

Lap times

get_lap_times

Inspect a driver's observed lap and sector times, with timestamps and pit flags.

Tyres

get_tyre_stints

Look up compounds, new or used sets, and reported tyre age.

Race control

get_race_control_messages

Search official text messages by time, driver, flag, category or phrase.

Pace comparison

compare_driver_pace

Compare recent laps, tyre context and pace gains, with exclusions and inputs for a conditional catch estimate.

Gap history

get_gap_history

Inspect a pair's recent race gaps and observed closing rate, with source timestamps and freshness checks.

Catch estimates

The pace tools provide the current race gap, recent comparable laps, pace variation and an observed gap trend. Your assistant can use those numbers to explain when a driver might close the gap.

Illustrative example · Not live timing

Gap: 6.0 seconds
Recent gain: 0.5 seconds / lap
Catch: ~12 laps

This assumes that relative pace continues. Traffic, tyre degradation, pit stops and flags can change the outcome; reaching another car does not guarantee a pass.

The tools flag stale or insufficient evidence and exclude observed pit and caution laps from pace comparisons. Practice and qualifying time differences are not treated as gaps between cars on track.

Data and coverage

Data comes from Formula 1's SignalR timing feed and recorded session history. Some session summaries also use Formula 1's own published timing archives. fastcarmaps does not scrape other live-timing dashboards.

Historical tools cover sessions captured by fastcarmaps, not every past race. Results include timestamps, missing values and coverage warnings. Live data depends on an active feed; a connected feed can still show a finished session. Lap deletion and eligibility checks are not yet complete.

Access is public and read-only, with bounded, rate-limited queries. F1 credentials stay on the server. Radio audio and transcripts are not available through these tools.

Prefer to follow the race visually? Open the live track map, explore circuit maps or read the timing guide.

Updated 2026-09-24. fastcarmaps is an independent project, not affiliated with Formula 1.