Skip to main content
Glama
dylangroos

NHL MCP Server

by dylangroos

Related Servers

Alternatives to NHL MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides live NHL data from the official NHL API, enabling users to fetch standings, scores, schedules, and player statistics.
      354 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides access to live NHL data including player statistics, team standings, game scores, schedules, and playoff information through 40+ NHL API endpoints.
      3
      -
    • A
      license
      B
      quality
      D
      maintenance
      Enables access to MLB Stats API data including game schedules, results, team information, and player lookups with fuzzy matching support through the Model Context Protocol.
      3
      7
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Provides Formula One data and statistics through a Model Context Protocol interface, allowing users to access race calendars, session results, driver statistics, telemetry data, and championship standings.
      8
      11
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time access to football (soccer) data including fixtures, standings, teams, players, transfers, and injuries through the API-Football service via the Model Context Protocol.
      3
      -
    • F
      license
      A
      quality
      D
      maintenance
      Provides access to live NHL game data, player and team statistics, standings, schedules, playoff brackets, and historical comparisons through natural language queries using the official NHL API.
      11
      -

    TDQS

    B3/5.0

    Scored across 25 tools

    Disambiguation3/5

    The tools have clear purposes within the NHL domain, but there is significant overlap that could cause confusion. For example, 'get-current-team-stats', 'get-team-stats', and 'get-team-stats-by-season' all retrieve team statistics with subtle distinctions, and multiple schedule tools (e.g., 'get-current-schedule', 'get-date-schedule', 'get-month-schedule') target similar data with different filters. Descriptions help differentiate, but agents might misselect due to these overlaps.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with 'get-' as the prefix, using snake_case throughout. This predictability makes it easy for agents to parse and understand the tool purposes, such as 'get-player-landing' or 'get-season-goalie-leaders'. There are no deviations in naming conventions across the set.

    Tool Count2/5

    With 25 tools, the count feels excessive for an NHL data server, leading to redundancy and potential bloat. Many tools could be consolidated into more flexible ones with parameters (e.g., a single schedule tool with date/team filters). This high number may overwhelm agents and complicate tool selection without adding proportional value.

    Completeness4/5

    The tool set covers a broad range of NHL data needs, including schedules, scores, standings, player and team statistics, rosters, and prospects. However, there are minor gaps, such as lack of tools for historical game data beyond play-by-play or detailed player career stats. Overall, it supports core workflows but could be more comprehensive for advanced queries.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues