🎩 You're Invited:Meet the Socket team at Black Hat in Las Vegas, August 3-6.RSVP
Sign In

pitstop-f1

Package Overview
Dependencies
Maintainers
1
Versions
1
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

pitstop-f1

All-in-one F1 MCP Server

pipPyPI
Version
0.5.0
Weekly downloads
27
35%
Maintainers
1
Weekly downloads
 

Pitstop — F1 MCP Server

An HTTP-first Model Context Protocol (MCP) server for Formula 1 data. Aggregates real-time, historical, and news data from multiple authoritative sources into 11 tools ready for any MCP client.

v0.5.0 | Author: Praneeth Ravuri

Install

stdio, via uvx (no clone needed):

PITSTOP_TRANSPORT=stdio uvx pitstop-f1

Via the Claude Code CLI:

claude mcp add pitstop -e PITSTOP_TRANSPORT=stdio -- uvx pitstop-f1

Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "pitstop": {
      "command": "uvx",
      "args": ["pitstop-f1"],
      "env": { "PITSTOP_TRANSPORT": "stdio" }
    }
  }
}

Docker (HTTP transport, runs the full server incl. the F1 database):

docker compose up
# → http://localhost:8000/mcp

Overview

Pitstop exposes F1 data as 11 MCP tools over HTTP (default) or stdio. It pulls from FastF1, Jolpica, OpenF1, Wikidata, RSS feeds, and its own seeded F1 database, handling pagination, retries, caching, and concurrency limits transparently.

Data Sources

SourceCoverageType
FastF12018–presentHistorical / timing / telemetry
Jolpica-F11950–presentHistorical (Ergast-compatible)
OpenF12023–presentReal-time
WikidataAll erasSPARQL queries
RSS Feeds (20 sources)LiveNews
Pitstop F1 Database1950–presentOwned sqlite (seeded from F1DB, self-updated weekly from Jolpica) + per-lap times

Database refresh: .github/workflows/db-update.yml runs weekly to pull new Jolpica results into the owned F1 database.

Tools

ToolDescriptionKey Parameters
get_session_dataRace/qualifying results, lap times, weather, driver details (2018–present)year, gp, session, includes, page, page_size
get_telemetry_dataLap-by-lap car telemetry (speed, throttle, brake, gears) (2018–present)year, gp, session, drivers, lap_numbers, max_points, page, page_size
get_live_dataLive intervals, pit stops, team radio, stints, race control, weather, position, laps, overtakes (2023–present)data_types, year, country, session_name, driver_number, compound, flag, category, page, page_size
get_standingsDriver and constructor championship standings (1950–present)year, round, type, driver_name, team_name, page, page_size
get_scheduleRace calendar and session scheduleyear, include_testing, round, event_name, only_remaining, page, page_size
get_reference_dataCircuits, drivers, constructors encyclopedia (1950–present)reference_type, year, name, page, page_size
get_f1_newsF1 headlines from 20 RSS sourcessource, limit, keywords, driver, team, circuit, year, date_from, date_to, page, page_size
get_resultsRace/qualifying/sprint results, lap times, pit stops (1950–present)year, round, result_type, driver, page
get_race_analysisPace, tire degradation, stint summaries, consistency (2018–present)year, gp, session, drivers, analysis_type, page
query_wikidataSPARQL queries to Wikidata for F1 biography, career records, historysparql, page, page_size
query_f1_databaseRead-only SQL over pitstop's owned F1 database (1950–present): results, standings, driver family trees, team lineagesql, page, page_size

Transport

HTTP (default)

uv sync
uv run pitstop
# → http://localhost:8000

MCP client config:

{
  "mcpServers": {
    "pitstop": {
      "type": "http",
      "url": "http://localhost:8000/mcp"
    }
  }
}

stdio (opt-in)

PITSTOP_TRANSPORT=stdio uv run pitstop

MCP client config:

{
  "mcpServers": {
    "pitstop": {
      "command": "uv",
      "args": ["run", "--directory", "/path/to/pitstop", "pitstop"],
      "env": { "PITSTOP_TRANSPORT": "stdio" }
    }
  }
}

Health API

EndpointPurpose
GET /healthPer-source status (FastF1, f1db, Jolpica, OpenF1, RSS)
GET /liveLiveness probe
GET /readyReadiness probe

Example /health response:

{
  "version": "0.5.0",
  "overall": "ok",
  "sources": [
    { "name": "fastf1",  "status": "ok", "latency_ms": 2,   "detail": "cache writable" },
    { "name": "f1db",    "status": "ok", "latency_ms": 1,   "detail": "" },
    { "name": "jolpica", "status": "ok", "latency_ms": 134, "detail": "" },
    { "name": "openf1",  "status": "ok", "latency_ms": 98,  "detail": "" },
    { "name": "rss",     "status": "ok", "latency_ms": 210, "detail": "" }
  ]
}

overall is "ok" / "degraded" / "down". HTTP 200 / 207 / 503.

Wikidata SPARQL

query_wikidata runs SPARQL queries against Wikidata for biographical and historical F1 facts not covered by race APIs.

Only SELECT and ASK queries are accepted (read-only). Always include LIMIT in your query.

Example — find F1 drivers with their birthdate:

SELECT ?driver ?driverLabel ?birthDate WHERE {
  ?driver wdt:P31 wd:Q5 ;
          wdt:P641 wd:Q1968 ;
          wdt:P569 ?birthDate .
  SERVICE wikibase:label { bd:serviceParam wikibase:language "en" }
} ORDER BY DESC(?birthDate) LIMIT 10

Pagination

All list-returning tools accept page (1-based, default 1) and page_size (defaults vary per tool: 10–50). Responses include a pagination block:

{
  "data": [...],
  "pagination": {
    "page": 1,
    "page_size": 20,
    "total_items": 47,
    "total_pages": 3,
    "has_next": true,
    "has_prev": false
  }
}

Configuration

VariableDefaultDescription
PITSTOP_TRANSPORThttphttp or stdio
PITSTOP_HOST0.0.0.0Bind address (HTTP only)
PITSTOP_PORT8000Listen port (HTTP only)
PITSTOP_ENVdevelopmentdevelopment or production
PITSTOP_LOG_LEVELDepends on PITSTOP_ENVDEBUG if development, else INFO
PITSTOP_LOG_FORMATDepends on PITSTOP_ENVtext if development, else json
PITSTOP_ENABLE_CACHINGtrueEnable HTTP response and FastF1 disk caching
PITSTOP_CACHE_TTL_SECONDS300HTTP response cache time-to-live (seconds)
PITSTOP_RATE_LIMIT_ENABLEDfalseEnable concurrent-call limiting
PITSTOP_RATE_LIMIT_PER_HOUR3600Max concurrent calls (derived from per-hour quota)
FASTF1_CACHEcacheFastF1 cache directory path

Caching

Pitstop uses in-memory HTTP response caching (via Hishel) for GET requests with 200 responses. This keeps tool calls inside upstream rate limits:

  • Jolpica: 4 req/s, 500/hr
  • OpenF1: 3 req/s, 30/min
  • Wikidata: Query complexity limits
  • RSS: Per-feed redirects cached

FastF1 maintains its own disk cache in FASTF1_CACHE directory. Control caching via:

  • PITSTOP_ENABLE_CACHING=true (default)
  • PITSTOP_CACHE_TTL_SECONDS=300 (default)

Development

uv sync --dev
uv run pytest
uv run ruff check src/

Contributing

See CONTRIBUTING.md.

Credits & attribution

SourceDescriptionLicense
F1DBDatabase seeded from F1DB and subsequently modified & extended by pitstopCC BY 4.0
FastF1Python library for F1 timing, telemetry, and session dataMIT
Jolpica-F1Ergast-compatible F1 data API, 1950–present; also used to self-update the F1DB-seeded database weekly
OpenF1Free open-source API for real-time F1 dataMIT
WikidataOpen knowledge graph with SPARQL query serviceCC0
Ergast Motor Racing APIHistorical F1 data 1950–2024 (now served via Jolpica)
RSS Feeds (20 sources)News headlines, credited collectively; see each feed's link field in get_f1_news resultsRespective publishers

Not affiliated with Formula 1 or the FIA. Data provided by third-party sources under their respective terms.

Keywords

f1

FAQs

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts