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
520,260 tools. Updated 2026-09-06 09:34
"Valorant" matching MCP tools:
- 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
- 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
Matching MCP Servers
- AlicenseNot gradedqualityBmaintenanceProvides VALORANT account and match data through HenrikDev's API. Enables querying profile, recent competitive matches, and match details.1MIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP-capable assistants to perform post-match Valorant analysis by inspecting stats, reviewing rounds and deaths, rendering tactical maps, and finding community lineups from a Riot ID or match link.-
- 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
- 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
- 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
- "What's the ticker for…" / "find the CIK for…" / "what's the LEI for…" / "what's the RxCUI for…" / "look up the ID for…" / "what is X's official identifier" / "who owns X" / "is X a subsidiary of Y" — resolve a user-spoken NAME to the canonical/official identifiers other tools require as input. Use FIRST whenever you have a name but need an ID. SUPPORTED TYPES: "company" (cross-source identity spine: 10-digit CIK + ticker + company_name from SEC EDGAR, legal-entity LEI from GLEIF with parent/ultimate-parent/children ownership when the LEI resolves, and security FIGI from OpenFIGI — by exact ticker map when a ticker is implied, and otherwise by name search, so NON-EQUITY instruments that never have a ticker (municipal and corporate bonds, notes, authority debt) DO resolve here; when a name matches more than one instrument it asserts nothing and returns `figi_candidates` to pick from, which is the correct answer to an issuer name that does not identify a single bond; every identifier is labelled with the source that established it, and an identifier that could NOT be resolved is stated explicitly under `unresolved` rather than omitted — accepts ticker, CIK, ISIN, or company name as input; an ISIN like "CH0038863350" resolves to the LEGAL ENTITY that issued the security via the GLEIF ISIN-to-LEI mapping, covering non-US issuers EDGAR cannot reach), "drug" (returns RxCUI + ingredient + brand from RxNorm + pipeworx://rxnorm/concept/{rxcui} citation; accepts brand or generic name). LEI/FIGI enrichment degrades gracefully — if GLEIF or OpenFIGI is unavailable, the EDGAR identifiers still return. Each call cascades through several lookup endpoints internally — using resolve_entity replaces 2-3 manual lookups.ConnectorNo auth
- "What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since `since`), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). `since` accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.ConnectorNo auth