mcpbeat

Race Calendar F1 MCP Server

app.racecalendar/f1
answering

Race Calendar F1 is answering right now. Last checked moments ago. It exposes 16 tools.

Anonymous read-only Formula 1 tools, resources, prompts, completion, and interactive dashboard.

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
92 of 92 checks
16
Tools
read from the server
592 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add f1 --transport http https://racecalendar.app/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "f1": {
      "url": "https://racecalendar.app/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.f1]
url = "https://racecalendar.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "f1": {
      "url": "https://racecalendar.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "f1": {
      "url": "https://racecalendar.app/mcp"
    }
  }
}

Available tools 16

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

historical
get_f1_historical_race_result
Get one complete historical Formula 1 race classification by season and championship round. Use only for a single race; for two or more races, call get_f1_historical_race_results once instead.
get_f1_historical_race_results
Get 2 to 8 complete historical Formula 1 race classifications in one consolidated request, with per-race sources and bounded partial failures. Use once for multi-race questions instead of repeating get_f1_historical_race_result.
race
get_f1_race_preview
Get a structurally spoiler-safe race-weekend briefing containing schedule and venue context but no classifications, winners, podiums, or result fields.
get_f1_race_weekend
Get one public Formula 1 race weekend by season and exactly one friendly selector: meeting key, round, race name, or slug.
session
get_f1_session_analysis
Get one strictly typed analysis view for a Formula 1 session: strategy, weather, timeline, or championship implications.
get_f1_session_results
Get the published classification for one Formula 1 session by season, meeting key, and session key, with positions and available result details.
circuit
get_f1_circuit
Get circuit metadata and normalized track geometry for a race weekend selected by meeting key, round, race name, or slug.
compare
compare_f1_competitors
Compare two Formula 1 drivers or constructors in one season using sourced standings and explicitly described calculations.
driver
get_f1_driver_session_summary
Get one driver's lap, sector, speed, grid, position, and interval summary for a Formula 1 session.
history
search_f1_history
Search the Formula 1 history index for drivers, teams, circuits, and races with bounded, cursor-based results.
live
get_f1_live_session
Get the latest explicitly timestamped status for the current or selected Formula 1 session. Returns unavailable rather than implying stale data is live.
next
get_f1_next_event
Find the next Formula 1 session or race weekend from a UTC timestamp, including an event already in progress.
season
get_f1_season_schedule
Get the verified public Formula 1 schedule for a season, including UTC session times, freshness, results, and canonical links.
standings
get_f1_standings
Get the public Formula 1 driver and constructor standings for a season with canonical source links.
starting
get_f1_starting_grid
Get the published starting grid for one Formula 1 session by season, meeting key, and session key; use session results for the final classification.
updates
get_f1_updates
Get recent public schedule, standings, and result changes after an optional timestamp or cursor.

Endpoints

URLTransportStateLatencyChecked
https://racecalendar.app/mcp streamable-http answering 1201 ms 0 min ago

Race Calendar F1 — questions

Answers built from our own checks of this server.

What can Race Calendar F1 do?
It exposes 16 tools, read directly from the server on our last check. Among them: compare_f1_competitors, get_f1_circuit, get_f1_driver_session_summary, get_f1_historical_race_result, get_f1_historical_race_results, get_f1_live_session and 10 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Race Calendar F1 mostly used for?
Its tools cluster around race, historical and session. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Race Calendar F1 working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 592 ms. The bar chart above shows every period we have measured.
How do I connect Race Calendar F1?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Race Calendar F1 need an API key?
No. Race Calendar F1 completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 16 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Race Calendar F1?
It answers our handshake in 592 ms on average, which is faster than 17% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.