# F1 (npm · @pipeworx/mcp-f1)

F1 MCP — Formula 1 data via the Ergast API

- Trust score: 85/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 78/100, [markdown](https://verifymcp.io/servers/pipeworx-io-f1/f1-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-f1/f1-mcp)
- npm · `@pipeworx/mcp-f1`: 85/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-f1/pipeworx-mcp-f1.md), [page](https://verifymcp.io/servers/pipeworx-io-f1/pipeworx-mcp-f1)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-f1`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-f1).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 287 tokens (~71/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the F1 MCP server?

F1 runs locally as an npm package, launched with npx -y @pipeworx/mcp-f1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-f1 -- npx -y @pipeworx/mcp-f1
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-f1": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-f1"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-f1": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-f1"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-f1 -- npx -y @pipeworx/mcp-f1
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-f1": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-f1"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-f1 --command npx --arg -y --arg @pipeworx/mcp-f1
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-f1:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-f1"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-f1": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-f1"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-f1 -t stdio -c npx -a -y @pipeworx/mcp-f1
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-f1": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-f1"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 85, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-11-04 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 83, +1)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Security disclosure: fail → unverified
- [functional improvement] Stability: unverified → 0.10
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 82, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 82)

First indexed and scored.

## MCP tools (4)

### `get_current_standings` (~35 tokens)

Check current F1 driver championship standings. Returns position, points, wins, driver name, and constructor for all drivers.

### `get_race_results` (~86 tokens)

Get race results for a specific F1 grand prix. Provide season year and round number (e.g., 2024, round 5). Returns finishing position, driver, constructor, status, and points.

Input parameters:

- `round` (string, required): Round number within the season (e.g., "1")
- `season` (string, required): Season year (e.g., "2025")

### `get_schedule` (~56 tokens)

Get the F1 season race calendar. Provide year (e.g., 2024). Returns all rounds with race name, circuit, location, and date.

Input parameters:

- `season` (string, required): Season year (e.g., "2025")

### `get_driver` (~58 tokens)

Look up F1 driver profile by ID. Returns name, car number, nationality, and date of birth.

Input parameters:

- `driverId` (string, required): Ergast driver ID (e.g., "hamilton", "verstappen", "leclerc")

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-f1/pipeworx-mcp-f1#diagnostics

## Score history

- 2026-11-05: 85
- 2026-11-04: 85
- 2026-11-03: 84
- 2026-11-02: 84
- 2026-11-01: 83
- 2026-10-31: 82
- 2026-10-30: 82
- 2026-10-29: 82

## Common questions

### What is the F1 MCP server?

F1 is an MCP server listed in the public MCP registry as io.github.pipeworx-io/f1. F1 MCP, Formula 1 data via the Ergast API. This page covers its npm package (@pipeworx/mcp-f1).

### Is the F1 MCP server safe to use?

F1 scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the F1 MCP server expose?

F1 exposes 4 tools: get_current_standings, get_race_results, get_schedule, get_driver. Their descriptions and schemas cost roughly 235 tokens of context every time the server is loaded.

### Is the F1 MCP server still maintained?

F1 is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the F1 MCP server under?

F1 declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the F1 MCP server?

VerifyMCP ran 15 checks on F1, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about F1: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-f1
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-f1
- Repository: https://github.com/pipeworx-io/mcp-f1
- Website: https://pipeworx.io/packs/f1
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-f1/pipeworx-mcp-f1.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-f1/pipeworx-mcp-f1/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-f1/pipeworx-mcp-f1.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-f1/pipeworx-mcp-f1