F1pitwall MCP Server

f1pitwall PyPI v1.1.0

Published by darshjoshi — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

F1 MCP server for Claude — 79 tools for live timing, telemetry, strategy, and 75 years of history. pip install f1pitwall[full] for plots.

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 79

Each tool and what it can reach — statically extracted from the published source.

  • analyze_brake_pointsno sensitive capability
  • analyze_drs_usageno sensitive capability
  • analyze_lap_consistencyno sensitive capability
  • analyze_long_run_paceno sensitive capability
  • analyze_rpm_datano sensitive capability
  • analyze_starting_tiresno sensitive capability
  • compare_grid_to_finishno sensitive capability
  • compare_sector_timesno sensitive capability
  • compare_strategiesno sensitive capability
  • compare_tire_age_performanceno sensitive capability
Show 69 more tools ↓
  • compare_tire_compoundsno sensitive capability
  • detect_overtakesno sensitive capability
  • get_championship_standingsno sensitive capability
  • get_circuit_infono sensitive capability
  • get_constructor_standingsno sensitive capability
  • get_deleted_lapsno sensitive capability
  • get_dnf_listno sensitive capability
  • get_driver_comparisonno sensitive capability
  • get_driver_infono sensitive capability
  • get_driver_standingsno sensitive capability
  • get_driver_tyre_detailno sensitive capability
  • get_fastest_lap_datano sensitive capability
  • get_fastest_pit_stopsno sensitive capability
  • get_fastest_sectorsno sensitive capability
  • get_gap_to_leaderno sensitive capability
  • get_historical_resultsno sensitive capability
  • get_lap_timesno sensitive capability
  • get_lap_times_fastf1no sensitive capability
  • get_live_best_sectorsno sensitive capability
  • get_live_gps_positionsno sensitive capability
  • get_live_lap_timesno sensitive capability
  • get_live_mini_sectorsno sensitive capability
  • get_live_pit_activityno sensitive capability
  • get_live_positionsno sensitive capability
  • get_live_race_controlno sensitive capability
  • get_live_sector_timesno sensitive capability
  • get_live_session_clockno sensitive capability
  • get_live_session_statusno sensitive capability
  • get_live_speed_comparisonno sensitive capability
  • get_live_speed_trapno sensitive capability
  • get_live_stint_historyno sensitive capability
  • get_live_telemetryno sensitive capability
  • get_live_time_gapsno sensitive capability
  • get_live_track_status_historyno sensitive capability
  • get_live_tyresno sensitive capability
  • get_live_weatherno sensitive capability
  • get_penaltiesno sensitive capability
  • get_personal_best_lapsno sensitive capability
  • get_pit_stop_detailno sensitive capability
  • get_pit_stopsno sensitive capability
  • get_position_changesno sensitive capability
  • get_qualifying_progressionno sensitive capability
  • get_race_controlno sensitive capability
  • get_race_control_messagesno sensitive capability
  • get_race_infono sensitive capability
  • get_race_resultsno sensitive capability
  • get_race_winners_historyno sensitive capability
  • get_scheduleno sensitive capability
  • get_session_infono sensitive capability
  • get_session_summaryno sensitive capability
  • get_speed_trap_comparisonno sensitive capability
  • get_speed_trapsno sensitive capability
  • get_sprint_resultsno sensitive capability
  • get_standingsno sensitive capability
  • get_stint_analysisno sensitive capability
  • get_team_lapsno sensitive capability
  • get_telemetryno sensitive capability
  • get_track_recordno sensitive capability
  • get_track_statusno sensitive capability
  • get_tyre_strategyno sensitive capability
  • get_weatherno sensitive capability
  • get_weather_datano sensitive capability
  • list_racesno sensitive capability
  • list_seasonsno sensitive capability
  • plot_driver_telemetry_comparisonno sensitive capability
  • plot_gear_shiftsno sensitive capability
  • plot_multi_telemetry_comparisonno sensitive capability
  • plot_telemetry_comparisonno sensitive capability
  • team_head_to_headno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.1.0 latest A 99/100 0 1.12.1 2026-07-27

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/f1pitwall/badge.svg)](https://mcptrustchecker.com/registry/f1pitwall)
HTML
<a href="https://mcptrustchecker.com/registry/f1pitwall"><img src="https://mcptrustchecker.com/registry/f1pitwall/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/f1pitwall/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan f1pitwall --online --registry pypi

Use the free API → How scoring works

More in Analytics & Monitoring