Retrieve Valorant leaderboard data for specific regions using the OP.GG MCP Server. Enables users to access ranked player standings by region for competitive insights.
MIT
466,528 tools. Updated 2026-08-19 16:37
"Valorant" matching MCP tools:
- Access Valorant character statistics, filtered by map, to analyze performance and improve gameplay strategies using data from OP.GG.MIT
- Get optimized Valorant agent compositions for specific maps using map ID. Enhance strategy by leveraging data from OP.GG for better in-game performance.MIT
- Access detailed match history for any Valorant player by entering their game name and tag line, enabling you to track performance and analyze gameplay trends.MIT
- Access detailed Valorant character meta data through the OP.GG MCP Server to optimize gameplay strategies and stay informed about agent performance trends.MIT
- Analyze Valorant map meta data to optimize strategies and enhance gameplay performance using OP.GG MCP Server’s AI-driven insights.MIT
Matching MCP Servers
- Alicense-qualityBmaintenanceProvides VALORANT account and match data through HenrikDev's API. Enables querying profile, recent competitive matches, and match details.1MIT
- Flicense-qualityDmaintenanceMCP server for Valorant esports that enables querying match schedules, live results, AI-powered analysis, and setting reminders.
- Solve authentication errors by setting your HenrikDev API key. This key enables Valorant API requests for player data, match history, and more.MIT
- Check Valorant service status for a region. View maintenance windows and active incidents to stay informed.MIT
- Obtain a Valorant player's PUUID, account level, player card, and region by entering their name, tag, and optional region code.MIT
- Look up a player's competitive leaderboard position and nearby players. Works for Immortal 3+ accounts using region codes ap, na, eu, kr, br, latam.MIT
- Retrieve the competitive leaderboard for a region. View top players with rankings and ratings for a specified season.MIT
- Retrieve a player's recent Valorant match history by entering their name and tag. Get detailed stats like kills, deaths, assists, agents, and maps.MIT
- Retrieve a Valorant player's current MMR, rank, ELO, and RR change by providing their name, tag, and region.MIT
- Correlate match performance with MMR changes to get a comprehensive competitive analysis. Understand how specific matches impact your rank with detailed match-by-match insights.MIT
- Retrieve a Valorant player's MMR history with match IDs, maps, rank changes, and dates for competitive analysis. Provide player name, tag, region, and optional size to get detailed historical data.MIT
- Get comprehensive stats for a Valorant match using match ID and region, including player performance, round outcomes, and final scores.MIT
- Retrieve a player's lifetime match statistics and match history for Valorant using their name, tag, and region. Filter results by mode or map and paginate through matches.MIT
- Retrieve Valorant game content including agents, maps, and weapons using a region code (ap, na, eu, kr, br, latam). Understand game elements for analysis or decision-making.MIT
- Retrieve a Valorant account by providing the player's game name and tag line. Returns account details for use in automated workflows.AGPL 3.0
- Cross-venue spread between Kalshi and Polymarket for the same resolving question. The two venues sometimes price the same outcome 2-25pp apart because their participant pools differ — when the bet shapes are equivalent that delta is a real signal, when they aren't the tool says so. TWO MODES: (1) `topic` — 10 pre-mapped macro shortcuts ("fed", "btc", "cpi", "gdp", "sp500", "recession", "next_pope", "next_uk_pm", "next_israel_pm", "2028_president") auto-fetch the matching event on each venue. (2) explicit `kalshi_event_ticker` + `polymarket_event_slug` for custom pairings. RESPONSE: each venue's leg-by-leg prices (raw probability 0-1) plus matched spread[].top_spreads_pp (Kalshi − Polymarket) where the same outcome shows up on both sides. SAFETY FIELDS: compatibility_warning fires in two cases — (a) matched_pairs:0 with skipped_cross_type>0 means the venues frame the topic with non-equivalent bet shapes (e.g. Kalshi range_bucket point-in-time vs Polymarket cumulative_threshold touch-anywhere — no arb exists), (b) matched_pairs:0 with skipped_cross_type:0 and both venues >5 legs means the token-overlap matcher found nothing in common — events likely semantically unrelated despite the topic keyword. temporal_alignment{polymarket_month,kalshi_month,aligned} tells you whether the two events resolve in the same calendar period; aligned:false means spreads are mathematically meaningless across the temporal gap. skipped_cross_type / skipped_cross_subtype counters expose how many leg-pair comparisons were dropped (cross-type = metric_type mismatch like MoM vs YoY; cross-subtype = inequality mismatch like cum_ge vs cum_le). Real cross-venue spreads are rarer than the macro-shortcut list suggests — most pre-mapped topics return compatibility_warning today; pre-mapped ≠ tradeable.Connector