@racehooks/mcp
OfficialRelated Servers
Alternatives to @racehooks/mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceMCP server for motorsport event documents, enabling AI agents to search, read, compare amendments, and parse schedules via typed tools.9-
- FlicenseNot gradedqualityBmaintenanceMCP server that provides Forza Horizon 5 telemetry tools (session listing, summaries, telemetry windows, tuning recommendations) to AI assistants, enabling natural language queries about driving sessions.-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that provides 118+ Formula 1 analytics tools, enabling race analysis, driver comparisons, telemetry exploration, and strategy simulation through natural language.MIT
- AlicenseAqualityBmaintenanceGives AI assistants structured access to racing-game telemetry such as lap and sector times, lap comparisons, braking zones and tyre wear through MCP tools and resources. It works out of the box on bundled synthetic sample data and can ingest a live F1 23 UDP feed.7MIT
- AlicenseCqualityDmaintenanceEnables AI assistants to access real-time iRacing telemetry, race information, camera control, pit operations, and replay features through the MCP protocol.171MIT
- AlicenseBqualityBmaintenanceMCP server that provides F1 telemetry analysis, tyre degradation modeling, and pit strategy recommendations, delivering race engineer-style calls grounded in real data. It exposes tools for degradation fits, fuel correction, and strategy reasoning via LangGraph.4MIT
TDQS
Scored across 58 tools
Most resource areas are distinct (webhooks, usage, races, drivers, replay), but the telemetry/analytics cluster has overlapping tools such as get_race_telemetry_laps vs get_telemetry_laps vs get_telemetry_driver_laps, and get_race_summary vs get_telemetry_race_summary. Descriptions help, but an agent could easily pick the wrong near-duplicate.
Mostly consistent snake_case with verb-first names (list_, get_, create_, update_, delete_, test_, rotate_, prepare_). There are minor ordering inconsistencies such as get_race_telemetry_laps vs get_telemetry_laps and the odd list_insight_races, but the pattern remains readable.
58 tools is very heavy for an MCP surface and includes many near-duplicate telemetry and usage variants. The broad F1 data platform scope explains some breadth, but the set is not tightly scoped and will make tool selection difficult.
Coverage is broad: live sessions, races, circuits, seasons, drivers, constructors, standings, telemetry, analytics, fantasy, replay, account usage/billing, and full webhook lifecycle including secrets and logs. Minor gaps remain, such as detailed feed introspection or finer-grained delivery operations, but core workflows are well covered.