Saltar al contenido
Logo de Race Calendar & Results

Servidor MCP de Race Calendar & Results

Qué servidores del registro oficial de MCP son de Race Calendar & Results, si responden y qué ofrecen. Un programa comprobó cada dato; nada está copiado de la página del producto.

leído el 2026-10-14

← Volver a Race Calendar & Results

De quién es el servidor
  • Nombre en el registroapp.racecalendar/f1verificado en el registro MCP

El nombre en el registro está bajo racecalendar.app. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

Cuando le preguntamoscomprobado el 2026-10-14
  • Estadorespondecomprobado el 2026-10-14
  • Herramientas15
  • El servidor se llamaracecalendar-f1
  • Versión del servidor4.0.1
  • Versión del protocolo2025-06-18

El 2026-10-14 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 208 ms.

Herramientas que ofrece15 herramientas · leído el 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.

Cómo conectar

Añade el servidor a la configuración de tu cliente MCP. Claude Desktop, Cursor y la mayoría de los demás clientes leen este formato:

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

Cada línea es algo que un programa encontró al buscar: la entrada del registro, la respuesta del propio servidor, una especificación que se puede leer. Si falta una línea, es que no la encontramos, no que no exista.