Summary
Hockey records without the HTML in the way.
Lookups return structured records — leagues, teams, rosters, player and staff profiles — so a question about a prospect's season is answered from data rather than from a page an assistant has to interpret. Players and staff are separate id spaces, and each profile points at the other when someone holds both.
What it is
Unofficial access to eliteprospects.com hockey data — leagues, teams, players and staff — as structured output rather than scraped HTML. One TypeScript core backs two front ends: a command-line tool, and an MCP server exposing the same lookups to clients such as Claude.
What you get
- Every league listed, filterable by a 2- or 3-letter country code (list_leagues)
- A single league with its metadata, teams and available seasons, optionally for one season (get_league)
- A team by id, with metadata, roster and available seasons (get_team)
- A player's profile by id: bio, draft and current team (get_player)
- A staff member's profile by id, with role and current team (get_staff)
- Player and staff kept in separate id namespaces, with each profile linking to the same person's other one
- No API key and no build step
Requirements
Bun, which runs the TypeScript directly. No API key.