mcpbeat Sign in

Race Calendar F1 MCP Server

by racecalendar Your server? Claim it
answering

Race Calendar F1 is answering right now. Last checked 11 min ago. It exposes 15 tools.

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

Uptime history 47 days of history
47 days agonow
100.0%
Uptime 24h
91 of 91 checks
15
Tools
read from the server
376 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 12 August 2026. No other catalogue keeps this.

12 Aug a tool changed version

Tools have disappeared from this server

A tool that vanishes takes a piece of your agent with it, and the change arrives silently. Watch this server and every such change lands in your inbox.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 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 15

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

race
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_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.
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.
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.
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.
session
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.
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 F1DB 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.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

get_f1_driver_session_summary
removed 5 Aug 2026
get_f1_session_analysis
removed 5 Aug 2026

Endpoints

URLTransportStateLatencyChecked
https://racecalendar.app/mcp streamable-http answering 613 ms 11 min ago

Alternatives to Race Calendar F1

same job, measured the same way
Brightspace
by jhostinaleck

MCP server for D2L Brightspace. Multi-auth, 26+ tools, MCP Resources, Prompts, and web dashboard.

117 installs/wk local only
Metricui
by mpmcgowen

React dashboard components — API lookup, code generation, and prop validation for AI tools.

32 installs/wk local only
ChartPane
by ahmadsl

Renders interactive Chart.js charts and dashboards inline in AI conversations.

answering
xrpldashboard
by xrpldashboard

Read-only XRP Ledger MCP tools with proof-annotation envelopes and signed daily snapshots.

15 tools answering
Logicmonitor
by ryanmat

LogicMonitor API integration with 167 tools for alerts, devices, dashboards, and more.

551 installs/wk local only
MCP Dashboards
by kyurish

45+ interactive charts, dashboards, flowcharts, and KPIs inside any AI conversation

425 installs/wk local only
LION Trend Intent MCP
by lionmaster20

Read-only x402-paid trend-intent MCP tools for JSON and CSV signals.

5 tools answering
MCP Sandbox Computer VM for AI
by flujo-app

Named Docker and Fly Machine sandbox computers with an interactive MCP App dashboard.

362 installs/wk local only

Race Calendar F1 — questions

Answers built from our own checks of this server.

What can Race Calendar F1 do?
It exposes 15 tools, read directly from the server on our last check. Among them: compare_f1_competitors, get_f1_circuit, get_f1_historical_race_result, get_f1_historical_race_results, get_f1_live_session, get_f1_next_event and 9 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 and historical. 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 91 of 91 checks got a reply (100.0%), average response time 376 ms. The bar chart above shows every period we have measured.
Did Race Calendar F1 ever remove tools?
Yes. get_f1_driver_session_summary, get_f1_session_analysis are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
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 15 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 376 ms on average, which is faster than 41% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.