Dappier Remote vs Pitwall — F1 Data for Claude
Dappier Remote is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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). As of our marketplace pass on 2026-10-13. 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
| Marketplace |  Dappier Remote |  Pitwall — F1 Data for Claude |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.1 Downloads/month (PyPI): 148 Downloads/week (PyPI): 42 Forks (GitHub): 1 Stars (GitHub): 9 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
| Fact | Dappier Remote | Pitwall — F1 Data for Claude |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 9 |
| Forks (GitHub) (differs) | No figure on GitHub | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.dappier.com/mcp) | On your machine (f1pitwall) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | Not a bundle | 2 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | Not stated | github.com/darshjoshi/pitwall |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 403 (9 h ago) | no remote endpoint we check |
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
Dappier Remote
Enable fast, free real-time web search and access premium data from trusted media brands—news, financial markets, sports, entertainment, weather, and more. Build powerful AI agents with Dappier.
Pitwall — F1 Data for Claude
F1 race engineer for Claude — 79 tools for live timing, telemetry, strategy, and 75 years of history
How to run each
Dappier Remote As a remote MCP server
claude mcp add --transport http dappier-remote https://mcp.dappier.com/mcpRequires: DAPPIER_REMOTE_API_KEY (secret)
Pitwall — F1 Data for Claude As a local MCP server: PyPI package
claude mcp add --transport stdio pitwall -- uvx f1pitwallCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Dappier Remote 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
The marketplaces of Pitwall — F1 Data for Claude publish no settings it asks for, so we do not compare settings.
What it can do: Dappier Remote · What it can do: Pitwall — F1 Data for Claude · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.