Skip to content
Back to the index

f1

pipeworx.ioInfrastructure

PulseGate's liveness check found it on 3 Oct 2026; it has been in the index since 22 Aug 2026. How this is checked

F1 is a Pipeworx-hosted MCP server that exposes tools for retrieving current driver championship standings, race results, season schedules, and driver profiles. It is intended for AI agents and developers integrating Formula 1 data through JSON-RPC over HTTP.

Inferred · not functionally tested

WebAPICloud-managed
f1 preview
Visit pipeworx.io

Overview

6 features

Purpose: Accessing live Formula 1 standings, race results, schedules, and driver profiles through AI agents.

Inferred · not functionally tested

Audience: AI agent developers and Formula 1 data users

Inferred · not functionally tested

Functions: data_extraction

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: unknown · Self-hosting: unknown

Recorded constraints: pricing: unknown · license: Proprietary · platforms: WEB · deployment: browser, api_only, cloud_managed

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: gateway.pipeworx.io. These links do not verify the individual claims.

f1 sits in PulseGate's API design, testing & docs category. Inferred · not functionally tested: It focuses on accessing live Formula 1 standings, race results, schedules, and driver profiles through AI agents. Inferred · not functionally tested: It is built as a B2B product for AI agent developers and Formula 1 data users. Basis unknown · not verified: It runs on the web and API.

Behind f1 is Pipeworx. Inferred · not functionally tested: Key capabilities include current standings, race results, and season schedule. Inferred · not functionally tested: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Current standings
  • Race results
  • Season schedule
  • Driver profiles
  • JSON-RPC endpoint
  • TypeScript samples

Topics: Inferred · not functionally tested

Tags
formula-one-datamcp-serverai-agent-toolssports-data-api

JSON profile · Text profile · Access guide

Built with & integrations

Hosting
Cloudflare
Connectors
MCP
Runs on
BrowserAPI-onlyCloud-managed
Detected from
Cloudflare
cf-ray header

Trust & compliance

Public signals
HTTPS

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed22 Aug · 00:56 UTC
    F1 seen via MCP Registry (official)
    Source: MCP Registry (official) · Open

Frequently asked questions about f1

What is f1?
Inferred · not functionally tested: F1 focuses on accessing live Formula 1 standings, race results, schedules, and driver profiles through AI agents. It is catalogued under API design, testing & docs on PulseGate.
Who should use f1?
Inferred · not functionally tested: f1 is a B2B product built for AI agent developers and Formula 1 data users.
What platforms does f1 run on?
Basis unknown · not verified: f1 runs on the web and API.
Is f1 still active?
PulseGate's liveness check found it on 3 Oct 2026.
What are alternatives to f1?
Similar projects tracked by PulseGate include fmp, fmi, and fpl-mcp.fmpfmifpl-mcp
Who makes f1?
f1 is developed by Pipeworx.
Does f1 have an API or integrations?
Inferred · not functionally tested: Yes — f1 exposes an MCP server.

Similar projects

Closest matches by what these projects do