Analytics

f1insightshub.com

Provides Formula 1 session, driver, and lap data with telemetry comparison and model-based insights for performance analysis.

1 endpoint9 known toolsFirst detected October 8, 2026Last detected October 8, 2026

ENDPOINT 1

https://mcp.f1insightshub.com/mcp

No auth detected

MCP server metadata

Name: f1insightshub
Version: 1.0.0

Capabilities

tools.listChanged

Server instructions

F1InsightsHub (f1insightshub.com) Formula 1 analysis tools. They return the same processed data and charts as the website's Analysis tab. Typical flow: 1. Identify the session. Every data tool accepts either session_key (from find_sessions) or year + event + session, e.g. {year: 2026, event: "Azerbaijan", session: "Qualifying"}. Event text can be a country, city, circuit or Grand Prix name. Session text can be "Q", "quali", "race", "sprint", "SQ", "FP1" and similar. 2. Drivers can be given by car number, three-letter code (VER), surname or full name. Call list_drivers when unsure. 3. Laps: get_laps lists each driver's laps with times, sectors, tyres and stints. In compare_telemetry a lap is a lap number or "fastest". 4. compare_telemetry is the telemetry comparison. It runs the site's distance-alignment pipeline and returns a per-corner breakdown (segment time, apex speed, braking point, throttle pickup), sampled channels, a full-resolution CSV link and charts. get_telemetry_insights adds the site's model-based strengths and weaknesses per lap. 5. For races and sprints: get_race_pace, get_lap_distribution, get_intervals. get_session_summary covers any session. Units: distance in metres from the start/finish line along the reference lap, speed in km/h, times in seconds. "gap_to_ref" and "delta_to_ref" are positive when the lap is slower (behind) the reference lap. Chart images come with a public link (valid about an hour) that you can show the user. Data comes from FastF1 timing and telemetry. A session that has not happened yet has no data. The first request for a session can take up to a minute or two while the server loads it.

Known tools 9

find_sessions

List F1 sessions in a season, optionally filtered by event (Grand Prix, country, city or circuit) and session (Qualifying, Race, Sprint, FP1…).

Inferred read-only

list_drivers

Drivers who took part in a session, with car number, code, team colour and finishing/classified position.

Inferred read-only

get_laps

Every lap for the chosen drivers: lap time, sector times, tyre compound, tyre age and stint, plus each driver's fastest lap and stint summary (average pace per stint).

Inferred read-only

compare_telemetry

Distance-aligned telemetry comparison of up to 8 laps, the website's Telemetry Analysis window.

Inferred read-only

get_telemetry_insights

Model-based insights for up to 8 laps, the website's Telemetry Insights panel.

Inferred read-only

get_race_pace

Average race pace per driver, the Analysis tab's Race Pace view: the mean of laps within the outlier threshold of each driver's best.

Inferred read-only

get_lap_distribution

Lap time distribution per driver, the Analysis tab's Sorted Laps view.

Inferred read-only

get_intervals

Gap to the race leader and position at the end of every lap per driver, the Analysis tab's Intervals view.

Inferred read-only

get_session_summary

The Analysis tab's Session Summary popup.

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.f1insightshub]
url = "https://mcp.f1insightshub.com/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: f1insightshub
Remote MCP URL: https://mcp.f1insightshub.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": {
    "f1insightshub": {
      "url": "https://mcp.f1insightshub.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

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

MCP Inspector

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

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

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