Ext Ops Panel
Open dashboard
Comparison

Pitwall — F1 Data for Claude vs F1

Pitwall — F1 Data for Claude is an MCP server published by darshjoshi. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). F1 is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplacePitwall — F1 Data for ClaudeF1
Official MCP Registry Listed
Version: 1.1.1
Downloads/month (PyPI): 148
Downloads/week (PyPI): 42
Forks (GitHub): 1
Stars (GitHub): 9
Not marked · First seen
Listed
Version: 0.1.2
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Pitwall — F1 Data for Claude vs F1
FactPitwall — F1 Data for ClaudeF1
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)9 (better)0 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (f1pitwall)Remote server (gateway.pipeworx.io/f1/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/darshjoshi/pitwallgithub.com/pipeworx-io/mcp-f1
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 18 h ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Pitwall — F1 Data for Claude

In its own words, on Official MCP Registry:

F1 race engineer for Claude — 79 tools for live timing, telemetry, strategy, and 75 years of history

F1

In its own words, on Official MCP Registry:

F1 MCP — Formula 1 data via the Ergast API

How to run each

Pitwall — F1 Data for Claude As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio pitwall -- uvx f1pitwall

F1 As a remote MCP server

Claude Code
claude mcp add --transport http f1 https://gateway.pipeworx.io/f1/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only F1 has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Pitwall — F1 Data for Claude · What it can do: F1 · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built