Index / MCP servers / Race Calendar F1

Race Calendar F1 MCP server

Connect Race Calendar F1 and your agent gets 15 tools, among them compare_f1_competitors, get_f1_circuit, get_f1_historical_race_result. It answers at https://racecalendar.app/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 17 October 2026, succeeded.

Status
Answering
Tools
15
Official
yes, served from racecalendar.app
Reliability
10 of 10 checks
Response time
467 ms
Transport
streamable HTTP
Last checked
17 October 2026

Anonymous read-only Formula 1 season schedule, standings, and race-weekend tools from Race Calendar.

Description as the publisher wrote it.

The 15 tools Race Calendar F1 offers

ToolWhat it does
compare_f1_competitorsCompare two Formula 1 drivers or constructors in one season using sourced standings and explicitly described calculations.
Inputs: competitorType, left, right, year
get_f1_circuitGet circuit metadata and normalized track geometry for a race weekend selected by meeting key, round, race name, or slug.
Inputs: meetingKey, raceName, round, slug, year
get_f1_historical_race_resultGet 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.
Inputs: round, year
get_f1_historical_race_resultsGet 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.
Inputs: races
get_f1_live_sessionGet the latest explicitly timestamped status for the current or selected Formula 1 session. Returns unavailable rather than implying stale data is live.
Inputs: meetingKey, sessionKey, year
get_f1_next_eventFind the next Formula 1 session or race weekend from a UTC timestamp, including an event already in progress.
Inputs: from, level, year
get_f1_race_classificationGet a published F1DB race, qualifying, or sprint classification by season and a friendly race selector, without requiring meeting or session keys.
Inputs: meetingKey, raceName, round, slug, year, classification
get_f1_race_previewGet a structurally spoiler-safe race-weekend briefing containing schedule and venue context but no classifications, winners, podiums, or result fields.
Inputs: meetingKey, raceName, round, slug, year
get_f1_race_weekendGet one public Formula 1 race weekend by season and exactly one friendly selector: meeting key, round, race name, or slug.
Inputs: meetingKey, raceName, round, slug, year
get_f1_season_scheduleGet the verified public Formula 1 schedule for a season, including UTC session times, freshness, results, and canonical links.
Inputs: year
get_f1_session_resultsGet the published F1DB classification for one Formula 1 session by season, meeting key, and session key, with positions and available result details.
Inputs: meetingKey, sessionKey, year
get_f1_standingsGet the public Formula 1 driver and constructor standings for a season with canonical source links.
Inputs: year
get_f1_starting_gridGet the published F1DB starting grid for one Formula 1 session by season, meeting key, and session key; use session results for the final classification.
Inputs: meetingKey, sessionKey, year
get_f1_updatesGet recent public schedule, standings, and result changes after an optional timestamp or cursor.
Inputs: cursor, limit, since
search_f1_historySearch the Formula 1 history index for drivers, teams, circuits, and races with bounded, cursor-based results.
Inputs: cursor, limit, query, types

Add Race Calendar F1 to your AI client

Every block below points at https://racecalendar.app/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http race-calendar-f1 https://racecalendar.app/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "race-calendar-f1": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://racecalendar.app/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "race-calendar-f1": {
      "url": "https://racecalendar.app/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "race-calendar-f1": {
      "type": "http",
      "url": "https://racecalendar.app/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "race-calendar-f1": {
      "url": "https://racecalendar.app/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "race-calendar-f1": {
      "serverUrl": "https://racecalendar.app/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "race-calendar-f1": {
      "url": "https://racecalendar.app/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Race Calendar F1
version: 0.0.1
schema: v1
mcpServers:
  - name: Race Calendar F1
    type: streamable-http
    url: https://racecalendar.app/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "race-calendar-f1": {
      "httpUrl": "https://racecalendar.app/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "race-calendar-f1": {
      "type": "http",
      "url": "https://racecalendar.app/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "race-calendar-f1": {
      "url": "https://racecalendar.app/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fracecalendar.app%2Fmcp&type=streamable_http&id=race-calendar-f1&name=Race%20Calendar%20F1

Is Race Calendar F1 up right now?

It answered our last check on 17 October 2026 in 467 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Race Calendar F1

Questions about Race Calendar F1

Is there an official Race Calendar F1 MCP server?

Yes. It is published by racecalendar.app and served from racecalendar.app, the vendor's own domain: https://racecalendar.app/mcp.

How many tools does Race Calendar F1 have?

15, as returned by the server's own tools/list on 9 September 2026: compare_f1_competitors, get_f1_circuit, get_f1_historical_race_result, get_f1_historical_race_results, get_f1_live_session, get_f1_next_event, get_f1_race_classification, get_f1_race_preview, and 7 more.

Is Race Calendar F1 down?

It answered our last check on 17 October 2026 in 467 ms. Over 10 checks since 4 September 2026 it answered 10.

How do I add Race Calendar F1 to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://racecalendar.app/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Race Calendar F1 need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: app.racecalendar. Endpoint host: racecalendar.app. ARD identifier: urn:air:app.racecalendar:mcp:f1. First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.