Skip to content
Race Calendar & Results logo

Race Calendar & Results MCP server

Which servers in the official MCP registry are Race Calendar & Results's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-14

← Back to Race Calendar & Results

Whose server it is
  • Registry nameapp.racecalendar/f1verified in the MCP registry

The registry name sits under racecalendar.app. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-14
  • Stateanswerschecked 2026-10-14
  • Tools15
  • Server calls itselfracecalendar-f1
  • Server version4.0.1
  • Protocol version2025-06-18

On 2026-10-14 the server answered initialize and tools/list without a sign-in. First answer in 208 ms.

Tools it offers15 tools · read 2026-10-14
  • get_f1_season_schedule

    Get the verified public Formula 1 schedule for a season, including UTC session times, freshness, results, and canonical links.

  • get_f1_standings

    Get the public Formula 1 driver and constructor standings for a season with canonical source links.

  • get_f1_next_event

    Find the next Formula 1 session or race weekend from a UTC timestamp, including an event already in progress.

  • get_f1_session_results

    Get the published F1DB classification for one Formula 1 session by season, meeting key, and session key, with positions and available result details.

  • get_f1_starting_grid

    Get the published F1DB starting grid for one Formula 1 session by season, meeting key, and session key; use session results for the final classification.

  • 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.

  • get_f1_race_classification

    Get a published F1DB race, qualifying, or sprint classification by season and a friendly race selector, without requiring meeting or session keys.

  • get_f1_circuit

    Get circuit metadata and normalized track geometry for a race weekend selected by meeting key, round, race name, or slug.

  • 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_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.

  • 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.

  • search_f1_history

    Search the Formula 1 history index for drivers, teams, circuits, and races with bounded, cursor-based results.

  • get_f1_updates

    Get recent public schedule, standings, and result changes after an optional timestamp or cursor.

  • compare_f1_competitors

    Compare two Formula 1 drivers or constructors in one season using sourced standings and explicitly described calculations.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "f1": {
      "type": "http",
      "url": "https://racecalendar.app/mcp"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.