Reference data alone is what a search engine already gives you. Having a player's recent matches — heroes played, performance, maps — next to the hero kits means a question like 'why am I losing on this map with this hero' can be answered against both what happened and what the character is supposed to do. The cosmetics coverage is broad to the point of completeness, which matters less but costs nothing. Straightforward read-only surface, and its usefulness tracks how current the underlying data is kept.
A Marvel Rivals reference and player-stats client covering four areas: heroes with their abilities and cosmetics, the item and skin catalogue, maps filterable by mode, and player profiles with match history.
- getHeroAbilities returns the ability kit including primary fire, and getHeroInfo adds stats, lore, difficulty rating and role.
- Cosmetics both ways round: getHeroSkins for one hero with rarity tiers, listSkins across the whole catalogue, listItems for nameplates, MVP animations, emotes and sprays, and getItemsByType to filter to one category.
- listMaps returns layouts, objectives and modes, and filterMaps narrows by game mode or queue type.
- Achievements listed with unlock conditions and points, and searchAchievement finds one by partial name.
- Player tools: searchPlayer by username or battletag, getPlayerProfile for rank, main heroes, win rates and playtime, and getPlayerMatchHistory for recent results with heroes, performance and maps.
Nothing to supply.
One command — npx @aimaginationlab/marvel-rivals-mcp