FighterAPI vs F1
FighterAPI is an MCP server published by noahowsh. Marketplaces we read that list it: 1 (Official MCP Registry). 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-17. 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 |   FighterAPI |  F1 |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.6 Forks (GitHub): 0 Stars (GitHub): 0 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
| Fact | FighterAPI | F1 |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-16 | Not published |
| Where it runs (differs) | Remote server (mcp.fighterapi.com/mcp) | Remote server (gateway.pipeworx.io/f1/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/noahowsh/fighterapi-mcp | github.com/pipeworx-io/mcp-f1 |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 18 h ago, requires a key | Responded 2 days 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
FighterAPI
UFC fights since 2000, plus PFL and Bellator: results, round stats, fighters and odds. REST and MCP.
F1
F1 MCP — Formula 1 data via the Ergast API
How to run each
FighterAPI As a remote MCP server
claude mcp add --transport http fighterapi https://mcp.fighterapi.com/mcp --header "x-api-key: <YOUR_X_API_KEY>"Requires: x-api-key header
F1 As a remote MCP server
claude mcp add --transport http f1 https://gateway.pipeworx.io/f1/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily 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: FighterAPI · What it can do: F1 · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.