UnClick beta: explore a historical racing lap

Learn to retrieve and check historical racing data with the UnClick OpenF1 standalone MCP. This is an educational setup example, not a hosted racing app or live timing service. UnClick is in beta.

SET UP Install Node.js with npm. In an MCP client supporting local stdio servers, use command npx with arguments ["-y", "@unclick/openf1-mcp@0.1.0"]. Merge this into your existing client configuration using that client's format, then restart or reconnect the server. The pinned package version was checked on 9 October 2026.

No provider account is needed for the historical query below. Live data has separate paid provider access; this package version has no token-authentication path.

TRY ONE LAP Tool: f1_laps Arguments: {"session_key":9839,"driver_number":44,"lap_number":1}

Ask your assistant: "Fetch this historical lap. Show the three sector times in seconds and check whether their sum equals lap_duration. Explain why one lap does not establish overall driver performance."

OBSERVED RESULT Sector 1: 24.475 seconds Sector 2: 39.820 seconds Sector 3: 35.449 seconds Total: 99.744 seconds, matching lap_duration.

Verified again on 9 October 2026 UTC through an MCP stdio test client using the unchanged published 0.1.0 package, Node.js 24.14.0 and MCP SDK 1.29.0. Startup, tool discovery and this historical lap query passed; the sector sum matched lap_duration. The session and driver identifiers come from OpenF1's documented example. The test reused installed dependencies, so fresh npx installation and graphical client setup remain untested. Live timing and other tools were not verified. This is historical data, not a current race result.

LIMITS TO KNOW Use this for personal learning and non-commercial analysis, following the provider's terms. OpenF1 is an independent community project, not an official Formula 1 service.

In version 0.1.0, f1_sessions silently ignores country_name and session_type, and f1_drivers ignores driver_number. The supported f1_laps filters in this example were checked. Do not rely on those other filters until repaired.

If npx cannot be found, check Node.js/npm and PATH. If a query fails, report the tool name and error without adding private credentials. Seeing tools in a client does not by itself prove provider access.

SOURCES AND NEXT STEP OpenF1 documentation: https://openf1.org/docs/ Provider example: https://openf1.org/ Explore UnClick's separate hosted beta, with Boardroom, memory and tools: https://unclick.world/connect The standalone package does not include the whole hosted platform.