Fastf1 (aashnakunk) MCP Server
fastf1-mcp
PyPI
v0.2.0
Published by aashnakunk — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Local MCP server for Formula 1 race intelligence — connect to Claude Desktop or any MCP-compatible client
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
low Shell/command execution in packaging/dev tooling (tests/test_mcp_protocol.py)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_mcp_protocol.py:23`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: f): self.proc = subprocess.Popen( [PYTHON, "-m", "f1_mcp"], stdin=subprocess.PIPE,
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server tests/test_mcp_protocol.py
Tools 17
Each tool and what it can reach — statically extracted from the published source.
driver_telemetryno sensitive capabilityfastest_lapsno sensitive capabilityhead_to_headno sensitive capabilityidentify_driverno sensitive capabilitylap_timesno sensitive capabilitylist_driversno sensitive capabilityload_sessionno sensitive capabilityovertake_analysisno sensitive capabilitypit_stopsno sensitive capabilityqualifying_resultno sensitive capability
Show 7 more tools ↓
race_resultno sensitive capabilityseason_calendarno sensitive capabilitysession_statusno sensitive capabilitysession_summaryno sensitive capabilitytire_stintsno sensitive capabilitytrack_evolutionno sensitive capabilityweatherno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (17 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.2.0 latest |
A 99/100 | 1 | 1.12.1 | 2026-07-27 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan fastf1-mcp --online --registry pypiOther implementations of Fastf1 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in Learning & Documentation
stdio compatibility bridge for the hosted AgentMail MCP server
MCP server for Alfa documentation retrieval
MCP server providing Alpine.js documentation and reference
Search the official Astro framework documentation.
MCP server providing ATAG 2.0 (Authoring Tool Accessibility Guidelines) guidance for authoring tool developers
Aurais Research Reader as an MCP server — paste a paper or article, get a structured read with verbatim-verified quotes + a signed Vorion proof chain (via @vorionsys/aurais-core).