Pitstop
概览
作者提供的说明(英文原文)
F1 MCP server: live timing, telemetry, standings, news, and a queryable 1950-present database.
PopNx MCP 的三大支柱
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
- 用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
- 我们的基础检查i1 项中通过 1 项依据公开信息检查;尚未扫描代码
- 使用情况i非常新↓ 15/周 · ★ –
它能帮你做什么
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
- 连接方式: 在你的电脑上运行
- 传输方式: stdio
- 分类: 搜索与 AI 记忆
- 你需要填写:PITSTOP_TRANSPORT
安装
选择你使用的 AI 应用,然后复制设置。
安装之前
- 基础检查:1 项中通过 1 项
- 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
- 需要你自己填写:
PITSTOP_TRANSPORT
你需要
- PyPI已安装 Python 的 uv(用于 uvx 命令)
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"pitstop": {
"command": "uvx",
"args": [
"pitstop-f1"
],
"env": {
"PITSTOP_TRANSPORT": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add pitstop --env PITSTOP_TRANSPORT=your-value -- uvx pitstop-f1运行前请先填写空着的值。
或者自己复制设置
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"pitstop": {
"command": "uvx",
"args": [
"pitstop-f1"
],
"env": {
"PITSTOP_TRANSPORT": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"pitstop": {
"type": "stdio",
"command": "uvx",
"args": [
"pitstop-f1"
],
"env": {
"PITSTOP_TRANSPORT": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
需要你填写的值
- Transport mode; must be 'stdio' when run via an MCP client.
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 praneethravuri 验证,该账户拥有此仓库
- … 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与“搜索与 AI 记忆”中的其他服务器比较i
- 星标数多于此分类中其他 5726 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 5726 个服务器的 20% 更新
- 基础检查结果等于或优于此分类中其他 5726 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
Pitstop 安全吗?
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
你需要填写:PITSTOP_TRANSPORT
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于–,最新版本(0.5.0)于4个月前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
有什么可以替代它?
同一分类中有:Context7, Codebase Memory, Exa
替代选择
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Codebase Memory
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Exa
Connect AI agents to Exa for web search, content fetching, and multi-step research.
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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
Hosted endpoint (nothing to install)
A free public instance runs on Hugging Face Spaces:
https://praneeth1025-pitstop.hf.space/mcp
claude mcp add --transport http pitstop https://praneeth1025-pitstop.hf.space/mcp
Note: the Space sleeps after long inactivity — the first request after a quiet spell takes a cold start.
Local install
stdio, via uvx (no clone needed):
PITSTOP_TRANSPORT=stdio uvx pitstop-f1
claude mcp add pitstop -e PITSTOP_TRANSPORT=stdio -- uvx pitstop-f1
codex mcp add pitstop --env PITSTOP_TRANSPORT=stdio -- uvx pitstop-f1
gemini mcp add pitstop uvx pitstop-f1 --env PITSTOP_TRANSPORT=stdio
VS Code:
code --add-mcp '{"name":"pitstop","command":"uvx","args":["pitstop-f1"],"env":{"PITSTOP_TRANSPORT":"stdio"}}'
Claude Desktop (claude_desktop_config.json), Cursor (~/.cursor/mcp.json), and Windsurf (~/.codeium/windsurf/mcp_config.json) share the same JSON shape:
{
"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
| Source | Coverage | Type |
|---|---|---|
| FastF1 | 2018–present | Historical / timing / telemetry |
| Jolpica-F1 | 1950–present | Historical (Ergast-compatible) |
| OpenF1 | 2023–present | Real-time |
| Wikidata | All eras | SPARQL queries |
| RSS Feeds (20 sources) | Live | News |
| Pitstop F1 Database | 1950–present | Owned 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
| Tool | Description | Key Parameters |
|---|---|---|
get_session_data | Race/qualifying results, lap times, weather, driver details (2018–present) | year, gp, session, includes, page, page_size |
get_telemetry_data | Lap-by-lap car telemetry (speed, throttle, brake, gears) (2018–present) | year, gp, session, drivers, lap_numbers, max_points, page, page_size |
get_live_data | Live 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_standings | Driver and constructor championship standings (1950–present) | year, round, type, driver_name, team_name, page, page_size |
get_schedule | Race calendar and session schedule | year, include_testing, round, event_name, only_remaining, page, page_size |
get_reference_data | Circuits, drivers, constructors encyclopedia (1950–present) | reference_type, year, name, page, page_size |
get_f1_news | F1 headlines from 20 RSS sources | source, limit, keywords, driver, team, circuit, year, date_from, date_to, page, page_size |
get_results | Race/qualifying/sprint results, lap times, pit stops (1950–present) | year, round, result_type, driver, page |
get_race_analysis | Pace, tire degradation, stint summaries, consistency (2018–present) | year, gp, session, drivers, analysis_type, page |
query_wikidata | SPARQL queries to Wikidata for F1 biography, career records, history | sparql, page, page_size |
query_f1_database | Read-only SQL over pitstop's owned F1 database (1950–present): results, standings, driver family trees, team lineage | sql, 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
| Endpoint | Purpose |
|---|---|
GET /health | Per-source status (FastF1, f1db, Jolpica, OpenF1, RSS) |
GET /live | Liveness probe |
GET /ready | Readiness 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
| Variable | Default | Description |
|---|---|---|
PITSTOP_TRANSPORT | http | http or stdio |
PITSTOP_HOST | 0.0.0.0 | Bind address (HTTP only) |
PITSTOP_PORT | 8000 | Listen port (HTTP only) |
PITSTOP_ENV | development | development or production |
PITSTOP_LOG_LEVEL | Depends on PITSTOP_ENV | DEBUG if development, else INFO |
PITSTOP_LOG_FORMAT | Depends on PITSTOP_ENV | text if development, else json |
PITSTOP_ENABLE_CACHING | true | Enable HTTP response and FastF1 disk caching |
PITSTOP_CACHE_TTL_SECONDS | 300 | HTTP response cache time-to-live (seconds) |
PITSTOP_RATE_LIMIT_ENABLED | false | Enable concurrent-call limiting |
PITSTOP_RATE_LIMIT_PER_HOUR | 3600 | Max concurrent calls (derived from per-hour quota) |
FASTF1_CACHE | cache | FastF1 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
| Source | Description | License |
|---|---|---|
| F1DB | Database seeded from F1DB and subsequently modified & extended by pitstop | CC BY 4.0 |
| FastF1 | Python library for F1 timing, telemetry, and session data | MIT |
| Jolpica-F1 | Ergast-compatible F1 data API, 1950–present; also used to self-update the F1DB-seeded database weekly | — |
| OpenF1 | Free open-source API for real-time F1 data | MIT |
| Wikidata | Open knowledge graph with SPARQL query service | CC0 |
| Ergast Motor Racing API | Historical 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 results | Respective publishers |
Not affiliated with Formula 1 or the FIA. Data provided by third-party sources under their respective terms.