Analytics

f1data.com

Provides Formula 1 racing data analysis including strategy, qualifying, and race replay insights.

1 endpoint28 known toolsFirst detected August 3, 2026Last detected August 3, 2026

ENDPOINT 1

https://f1data.com/mcp

No auth detected

MCP server metadata

Name: f1data
Version: 0.1.0

Capabilities

tools

Known tools 28

analyze_strategy

Quantitative strategy analysis of a race: per-compound tyre degradation (s/lap fitted from clean-air stint laps), pit-loss estimate, and every pit stop's realized undercut gain/loss vs the car ahead.

Inferred read-only

analyze_qualifying

Deep qualifying analysis for a Grand Prix: Q1→Q2→Q3 time progression per driver, gap to pole in each segment, who was knocked out where, and track evolution (how much faster the track got each segment).

Inferred read-only

qualifying_head_to_head

Season-long qualifying duel between two drivers: who out-qualified whom each round, the running score, average gap, and current streak.

Inferred read-only

get_track_dominance

Track dominance map: the circuit coloured by which driver is fastest in each mini-sector, computed from GPS + speed telemetry on each driver's fastest lap.

Inferred read-only

get_race_replay

Show an animated track-map replay of a race: every car moving around the circuit, scrubbable lap by lap.

Inferred read-only

compare_telemetry

Compare two drivers' car telemetry (speed, throttle, brake, gear) over one lap each, aligned side by side with corner markers - shows exactly where time is gained and lost.

Inferred read-only

create_chart

Create a custom chart from a SQL query when no purpose-built tool fits - season trends, custom aggregations, any visualization the user asks for.

Potential side effects

get_race_trace

The classic race-trace chart: every driver's gap to the leader over the laps of a race.

Inferred read-only

get_position_chart

Position evolution chart: every driver's running position lap by lap through a race.

Inferred read-only

analyze_season_pace

Cross-race pace analysis: rank drivers or teams by representative race pace over multiple Grands Prix.

Inferred read-only

get_battle_gaps

How close a fight was: each driver's gap to the car AHEAD over the race, from ~4-second interval data.

Inferred read-only

list_races

List all Grands Prix of a season with dates and locations.

Inferred read-only

get_race_results

Official final classification of a Grand Prix race: positions, gaps, points, grid, status (Finished/DNF/etc.), fastest lap.

Inferred read-only

get_qualifying_results

Qualifying classification with Q1/Q2/Q3 lap times for a Grand Prix.

Inferred read-only

get_sprint_results

Sprint race classification for a sprint-format Grand Prix weekend.

Inferred read-only

get_standings

Drivers or constructors championship standings, either current or as they stood after a specific race.

Inferred read-only

get_title_chances

Championship title math: points remaining in the season, who is still mathematically in the fight (drivers and constructors), elimination status and what challengers need.

Inferred read-only

get_strategy

Tyre strategy of a race: every driver's stints (compound, laps, tyre age) and pit stops with durations.

Inferred read-only

compare_pace

Compare race pace between drivers in a session: average/median/best lap, consistency.

Inferred read-only

get_lap_times

Lap-by-lap times for specific drivers in a race, including sector times.

Inferred read-only

get_race_story

Key events of a race in chronological order: flags, safety cars, red flags, penalties and investigations from race control.

Inferred read-only

get_weather

Weather during a session: air/track temperature, rainfall, wind, humidity summarized over the session.

Inferred read-only

get_weather_timeline

Weather evolution through a session as a timeline: track/air temperature and rainfall sampled every ~2 minutes.

Inferred read-only

get_overtakes

On-track overtakes in a race: per-driver counts of overtakes made and suffered, plus the busiest laps.

Inferred read-only

get_team_radio

Team radio clips from a session: driver, timestamp and a playable MP3 link for each message.

Potential side effects

analyze_practice

Practice long-run analysis: race-sim pace (median of stints of 5+ laps) per driver and compound across the practice sessions, with lap counts.

Inferred read-only

get_position_changes

Grid position vs finishing position for every driver in a race - who gained and lost the most places.

Inferred read-only

query_database

Escape hatch: run a read-only SQL query against the F1 database for questions no other tool covers.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.f1data]
url = "https://f1data.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "f1data": {
      "type": "http",
      "url": "https://f1data.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: f1data
Remote MCP URL: https://f1data.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "f1data": {
      "url": "https://f1data.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "f1data": {
      "type": "http",
      "url": "https://f1data.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "f1data",
  "transport": "streamable-http",
  "url": "https://f1data.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for f1data.com was fetched 2026-08-08T10:49:23.196Z and is being refreshed.

Trust status New

This domain appears to have previously been parked, so its current status is new or unverified.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.