MCP.Market

Pitwall — F1 Data for Claude MCP server

by darshjoshi·io.github.darshjoshi/pitwall·v1.1.1·8 stars

F1 race engineer for Claude — 79 tools for live timing, telemetry, strategy, and 75 years of history

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

8 stars22 downloads/wk

Reviews

Write one

Nobody has reviewed Pitwall — F1 Data for Claude yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Pitwall — F1 Data for Claude tools (79, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • analyze_brake_points

    Analyze braking patterns on fastest lap.

  • analyze_drs_usage

    Analyze DRS usage on a driver's fastest lap.

  • analyze_lap_consistency

    Analyze lap time consistency (standard deviation, variation).

  • analyze_long_run_pacewrite action

    Analyze race simulation pace from practice sessions.

  • analyze_rpm_data

    Analyze engine RPM patterns on fastest lap.

  • analyze_starting_tires

    Analyze which tire compounds were used at race start.

  • compare_grid_to_finish

    Compare starting grid positions to finishing positions.

  • compare_sector_times

    Compare sector times between two drivers.

  • compare_strategies

    Compare tire strategies between two drivers.

  • compare_tire_age_performance

    Compare lap times on fresh vs used tires.

  • compare_tire_compounds

    Compare average lap times across different tire compounds.

  • detect_overtakes

    Detect when a driver overtook others (position gained between laps).

  • get_championship_standings

    Get championship standings from 1950 to present.

  • get_circuit_info

    Get track layout info (Corners, DRS Zones).

  • get_constructor_standings

    Get constructor/team championship standings.

  • get_deleted_laps

    Get all laps deleted due to track limits or other violations.

  • get_dnf_list

    Get list of drivers who did not finish the race and reasons.

  • get_driver_comparison

    Compare two drivers head-to-head — position, pace, strategy, pit stops.

  • get_driver_info

    Get detailed driver information (number, team, headshot, etc.).

  • get_driver_standings

    Get driver championship standings after a specific round or latest.

  • get_driver_tyre_detail

    Get detailed tyre stint data for a specific driver via FastF1 — compound, laps, and degradation.

  • get_fastest_lap_data

    Get detailed stats for a driver's fastest lap (Sector times, Speed trap).

  • get_fastest_pit_stops

    Get the fastest pit stops of the race, ranked by stationary time.

  • get_fastest_sectors

    Find who set the fastest time in each sector.

  • get_gap_to_leader

    Track gap to race leader throughout the race.

  • get_historical_results

    Get historical F1 race results from 1950 to present.

  • get_lap_times

    Get lap-by-lap times for one or all drivers. Filterable by lap range.

  • get_lap_times_fastf1

    Get all lap times for a driver via FastF1 — includes compound and tyre life per lap.

  • get_live_best_sectors

    Live personal-best sector times and overall best lap per driver, ranked by lap position. No auth required.

  • get_live_gps_positions

    Live circuit-relative GPS coordinates — raw x/y integers for every car, a snapshot of the current instant. NOT mapped to named corners (no x/y-to-corner model). Requires a valid F1 TV token.

  • get_live_lap_times

    Live last + best lap time per driver. No auth required.

  • get_live_mini_sectors

    Live mini-sector status per driver: g=green/personal-best, p=purple/overall-best, y=yellow, .=no data. No auth required.

  • get_live_pit_activity

    Live pit-stop count and real-time in-pit / out-lap flags per driver. No auth required.

  • get_live_positions

    Live running order with gap-to-leader and interval. No auth required.

  • get_live_race_control

    Live race control: flags, penalties, track-limit deletions, SC/VSC. No auth required.

  • get_live_sector_times

    Live sector times + speed trap for one driver (TLA or car number). No auth required.

  • get_live_session_clock

    Live time remaining in the current session. No auth required.

  • get_live_session_status

    Live F1 session status: session name, flag/track status, lap count. No auth required. Honest 'no live session' message when nothing is running.

  • get_live_speed_comparison

    Live best speed at each measurement point (I1, I2, FL, ST) for every driver. No auth required.

  • get_live_speed_trap

    Live speed-trap (ST) ranking across the whole field. No auth required.

  • get_live_stint_history

    Live full compound sequence and stint lengths for every driver in track-position order. No auth required.

  • get_live_telemetry

    Live car telemetry — the LATEST single sample (speed/rpm/gear/throttle/brake) for one driver: a snapshot of the current instant, NOT a lap trace and NOT resolved to a track corner. No DRS in 2026 (active aero). Auth-gated: needs a valid F1 TV token (CarData.z) AND cars on track. For a corner-by-corner lap trace use the post-session tool get_telemetry(driver, lap=N).

  • get_live_time_gaps

    Live gap to leader and interval to car ahead per driver, mode-aware (race gap vs quali/practice fastest). No auth required.

  • get_live_track_status_history

    Live chronological log of track-status and session-status changes. No auth required.

  • get_live_tyres

    Live tyre compound, age (laps), and stint number per driver. No auth required.

  • get_live_weather

    Live track weather (air/track temp, humidity, wind, rain). No auth required.

  • get_penalties

    Get all penalties issued during the race.

  • get_personal_best_laps

    Get each driver's personal best lap time.

  • get_pit_stop_detail

    Get detailed pit stop data — stationary time, pit-lane time, and tyre compound swap per stop.

  • get_pit_stops

    Get all pit stops sorted by fastest stop time.

  • get_position_changes

    Track position changes throughout the race for a driver.

  • get_qualifying_progression

    Show who was eliminated in Q1, Q2 and who made it to Q3.

  • get_race_control

    Get race control messages — flags, penalties, safety cars, investigations.

  • get_race_control_messages

    Get all race control messages during a session.

  • get_race_info

    Get session details and list of available data feeds.

  • get_race_results

    Get the final classification (Position, Driver, Team, Points).

  • get_race_winners_history

    Get race winners for a specific GP over the last N years.

  • get_schedule

    Get the full race calendar for a specific year (excluding testing).

  • get_session_info

    Get start time and status of a specific session (R=Race, Q=Quali, FP1, etc).

  • get_session_summary

    Get a comprehensive quick summary of a session.

  • get_speed_trap_comparison

    Compare speed trap data across all drivers.

  • get_speed_traps

    Get speed trap readings at 4 measurement points (I1, I2, FL, ST) per driver.

  • get_sprint_results

    Get sprint race results (for sprint weekends).

  • get_standings

    Get race classification — positions, gaps, best laps, pit stops, retirements.

  • get_stint_analysis

    Analyze each stint: compound, lap times, degradation.

  • get_team_laps

    Get all laps for a specific team (both drivers).

  • get_telemetry

    Get car telemetry — speed, RPM, throttle, brake, gear, DRS for a specific lap.

  • get_track_record

    Get the all-time lap record for a specific circuit (via Ergast).

  • get_track_status

    Get track status changes (yellow flags, safety car, red flag, etc.).

  • get_tyre_strategy

    Get tyre strategy for every driver — compound, stint length, new/used tyres.

  • get_weather

    Get weather conditions during a session — temperature, rain, wind, humidity.

  • get_weather_data

    Get detailed weather conditions (Rain, Track Temp, Wind).

  • list_races

    List all races and sessions for a season with dates and session paths.

  • list_seasons

    List all available F1 seasons (2018-present).

  • plot_driver_telemetry_comparison

    Plot comprehensive telemetry comparison (speed, throttle, brake, gear) between two drivers for the same lap.

  • plot_gear_shifts

    Generates a Gear Shift chart for a single driver.

  • plot_multi_telemetry_comparison

    Compare full telemetry (speed, throttle, brake, gear) between two laps for same driver. Example: Compare first lap vs last lap for Piastri Brazil 2024

  • plot_telemetry_comparison

    Generates a Speed Trace comparison image between two drivers. Returns: An ImageContent object that can be displayed in the client.

  • team_head_to_head

    Compare both drivers in a team head-to-head.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan7 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 53 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Pitwall — F1 Data for Claude compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers
Tools
79
the typical server has 7
Tools that change things
1%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
8
more than 86% of 28,688 servers
Downloads a week
22
more than 8% of 12,191 servers with a package

What its tools let an agent do: 78 read · 1 change

Install Pitwall — F1 Data for Claude in Claude Code, Cursor or VS Code

claude mcp add pitwall -- uvx f1pitwall
Add to Cursor

What the publisher says

From the Pitwall — F1 Data for Claude repository's README, as published. We do not edit it. Read it on GitHub

<!-- mcp-name: io.github.darshjoshi/pitwall --> Pitwall

Turn Claude into your F1 race engineer. Real telemetry. Real strategy data. 75 years of history.

Quick Start

Claude Code — one command, all 79 tools:

claude mcp add pitwall -- uvx --from "f1pitwall[full]" f1pitwall

Then ask Claude: "Who won the 2025 Australian GP?"

Needs uv (curl -LsSf https://astral.sh/uv/install.sh | sh). No pip, no virtualenv, no "which python3" — and you always get the latest release.

First launch downloads the FastF1 stack (~540 MB) and takes about 25 seconds. Every launch after that is under a second. If the very first start times out, just restart Claude Code — the download is already cached.

Want the plugin instead, so you get the f1 skill along with the server? See Install as a Claude Code plugin.

Lighter install (30 tools, no plots)

Skips pandas/numpy/matplotlib/FastF1. Still includes all 16 live-timing tools.

claude mcp add pitwall -- uvx --from f1pitwall f1pitwall

Install with pip instead

pip install "f1pitwall[full]"        # or just f1pitwall for lite
claude mcp add pitwall -- f1pitwall

Install from source instead

git clone https://github.com/darshjoshi/pitwall.git && cd pitwall
pip install -r requirements.txt        # lite (incl. live timing)
pip install -r requirements-full.txt   # full
claude mcp add pitwall -- python3 $(pwd)/pitwall.py

Install as a Claude Code plugin

The plugin ships the MCP server and the f1 skill together — the skill teaches Claude which of the 79 tools to reach for and how to explain F1 to someone who's never watched a race.

/plugin marketplace add darshjoshi/pitwall
/plugin install pitwall@pitwall

Claude Desktop

Add to claudedesktopconfig.json (Settings → Developer → Edit Config):

{
  "mcpServers": {
    "pitwall": {
      "command": "uvx",
      "args": ["--from", "f1pitwall[full]", "f1pitwall"]
    }
  }
}

Why Pitwall?

Claude knows F1 from training data — but it can't look up last week's race. It can't show you Verstappen's throttle trace through Turn 1. It doesn't know who pitted first or when the safety car came out.

Pitwall connects Claude to real F1 data:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Pitwall — F1 Data for Claude: common questions

Is Pitwall — F1 Data for Claude MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Pitwall — F1 Data for Claude safety report
How do I install Pitwall — F1 Data for Claude?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Pitwall — F1 Data for Claude need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Pitwall — F1 Data for Claude maintained?
The last commit was 94 days ago (2026-08-02). The latest release is v1.1.1.
How does Pitwall — F1 Data for Claude compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); tools 79 (the typical server has 7); tools that change things 1% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.