{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-op-gg","slug":"op-gg","name":"OP.GG","type":"mcp","url":"https://github.com/opgginc/opgg-mcp","page_url":"https://unfragile.ai/op-gg","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-op-gg__cap_0","uri":"capability://tool.use.integration.stdio.to.http.mcp.protocol.bridging.with.transparent.request.forwarding","name":"stdio-to-http mcp protocol bridging with transparent request forwarding","description":"Implements a bidirectional Model Context Protocol proxy that accepts stdio connections from local MCP clients (Claude Desktop, Cursor, etc.) and transparently forwards all tool calls over Streamable HTTP to a remote OP.GG MCP endpoint at https://mcp-api.op.gg/mcp. Uses StdioServerTransport for local consumer communication and StreamableHTTPClientTransport for outbound HTTP, with dynamic capability discovery at startup to mirror remote tools into the local server's tool registry without hardcoding tool definitions.","intents":["Connect local AI agents to remote gaming data APIs without modifying client code","Run OP.GG gaming tools inside Claude Desktop or other stdio-based MCP clients","Proxy MCP requests through a local process to avoid direct HTTP exposure in client configs"],"best_for":["AI agent developers integrating gaming data into Claude or Cursor workflows","Teams deploying MCP servers in restricted network environments requiring local proxies","Builders wanting transparent HTTP-to-stdio adaptation without custom integration code"],"limitations":["Adds network round-trip latency for every tool call (remote HTTP request to https://mcp-api.op.gg/mcp)","No local caching or request deduplication — each tool call results in a fresh HTTP request","Requires network connectivity to remote OP.GG endpoint; no offline fallback or graceful degradation","Single-threaded stdio processing means concurrent requests from multiple clients will queue sequentially"],"requires":["Node.js runtime (version not specified in docs, but dist/index.js implies Node 14+)","Network access to https://mcp-api.op.gg/mcp endpoint","MCP client supporting stdio transport (Claude Desktop, Cursor, or custom MCP client)","Optional: Smithery configuration file (smithery.yaml) for automated process spawning, or manual npm/npx invocation"],"input_types":["MCP tool call requests (JSON-RPC 2.0 format over stdin)","Tool parameters matching remote OP.GG tool schemas"],"output_types":["MCP tool call responses (JSON-RPC 2.0 format over stdout)","Structured gaming data (champion stats, match history, leaderboards, esports schedules)"],"categories":["tool-use-integration","mcp-protocol"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-op-gg__cap_1","uri":"capability://data.processing.analysis.league.of.legends.champion.and.summoner.data.querying.with.field.level.filtering","name":"league of legends champion and summoner data querying with field-level filtering","description":"Exposes 15 tools for querying League of Legends game data including champion statistics, summoner profiles, match history, resource guides, pro player stats, and esports schedules. Each tool accepts a desired_output_fields parameter to filter response payloads at the API level, reducing bandwidth and token consumption by excluding unnecessary fields. Tools are prefixed with 'lol_' and cover champion analytics, summoner rank/win rates, match timelines, and competitive esports data.","intents":["Fetch real-time champion win rates, ban rates, and meta build recommendations for a specific rank tier","Look up summoner profiles and match history to analyze player performance patterns","Query esports schedules, team rosters, and pro player statistics for competitive League content","Retrieve champion ability descriptions and item build guides for in-game decision support"],"best_for":["Gaming content creators building League of Legends analysis tools or guides","Esports analysts automating match research and player performance tracking","AI agents providing real-time meta recommendations to players during champion select","Developers building Discord bots or Twitch extensions with live League data"],"limitations":["Data freshness depends on OP.GG's update frequency (typically 5-15 minute delay from live matches)","Summoner lookups require exact summoner name and region; fuzzy matching not supported","Match history limited to recent matches (typically last 100-200 matches); full historical data not available","Pro player and esports data may lag behind live events by several minutes","No real-time in-game data (current game state, live position tracking) — only completed match data"],"requires":["Valid summoner name and region (e.g., 'NA', 'EUW', 'KR') for summoner-specific queries","Champion name or ID for champion-specific analytics","Optional: desired_output_fields array to specify which response fields to include (e.g., ['winRate', 'pickRate', 'banRate'])"],"input_types":["Summoner name (string)","Region code (string: 'NA', 'EUW', 'KR', etc.)","Champion name or ID (string or integer)","Rank tier filter (string: 'DIAMOND', 'PLATINUM', etc.)","desired_output_fields (array of field names for response filtering)"],"output_types":["Champion statistics (win rate, pick rate, ban rate, average KDA, item builds)","Summoner profile data (rank, LP, win rate, main champions, match history)","Match details (participants, kills/deaths/assists, items built, duration, outcome)","Pro player stats and esports schedule data (team, tournament, match results)"],"categories":["data-processing-analysis","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-op-gg__cap_10","uri":"capability://automation.workflow.installation.and.deployment.via.smithery.npm.or.docker","name":"installation and deployment via smithery, npm, or docker","description":"Supports three deployment methods: (1) Smithery configuration via smithery.yaml for automated process spawning, (2) manual npm/npx invocation (npx opgg-mcp or node dist/index.js), and (3) Docker deployment for containerized environments. All methods ultimately execute dist/index.js as a local stdio MCP server process. Enables flexible deployment across different environments (local development, CI/CD pipelines, containerized infrastructure) without code changes.","intents":["Deploy the OP.GG MCP proxy in local development environments using npm/npx","Integrate the proxy into Smithery-based MCP client configurations for automated process management","Deploy the proxy in containerized environments (Docker, Kubernetes) for production use","Support multiple deployment patterns without requiring code modifications"],"best_for":["Individual developers integrating OP.GG data into Claude Desktop or Cursor","Teams using Smithery for MCP server management and orchestration","Organizations deploying MCP proxies in containerized infrastructure (Docker, Kubernetes)","CI/CD pipelines that need to spawn MCP servers as part of automated workflows"],"limitations":["Smithery installation requires Smithery client and smithery.yaml configuration; not suitable for non-Smithery environments","npm/npx installation requires Node.js and npm; not suitable for environments without Node.js runtime","Docker deployment requires Docker runtime and image building; adds complexity for simple use cases","No built-in process management (restart on failure, health checks); requires external orchestration for production use","Installation documentation may be incomplete or outdated; refer to README.md for latest instructions"],"requires":["For Smithery: Smithery client installed, smithery.yaml configuration file","For npm/npx: Node.js 14+ and npm, or npx (bundled with npm 5.2+)","For Docker: Docker runtime, Dockerfile (provided in repo), and Docker image build capability","Network access to https://mcp-api.op.gg/mcp for all deployment methods"],"input_types":["Smithery configuration (smithery.yaml with opgg-mcp server definition)","npm/npx command invocation (npx opgg-mcp or node dist/index.js)","Docker image and container configuration"],"output_types":["Running MCP server process listening on stdio","MCP tools available to local clients (Claude Desktop, Cursor, etc.)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-op-gg__cap_2","uri":"capability://data.processing.analysis.teamfight.tactics.meta.composition.and.augment.analysis.with.play.style.filtering","name":"teamfight tactics meta composition and augment analysis with play style filtering","description":"Provides 6 tools for querying Teamfight Tactics (TFT) game data including meta deck compositions, item builds, augment recommendations, and play style classifications. Tools are prefixed with 'tft_' and return structured data about optimal team compositions for the current TFT set, itemization strategies, and augment synergies. Supports filtering by play style (e.g., 'aggressive', 'control', 'economy') and rank tier to surface meta-relevant recommendations.","intents":["Get current meta deck compositions and win rates for the active TFT set","Query optimal item builds and augment combinations for specific team compositions","Filter meta recommendations by play style (aggressive vs. economy-focused) and rank tier","Build AI coaching agents that recommend real-time team pivots based on current meta"],"best_for":["TFT content creators and streamers building real-time meta guides","AI agents providing in-game coaching recommendations during TFT matches","Esports analysts tracking meta shifts across tournament patches","Mobile app developers integrating TFT strategy guides"],"limitations":["Meta data updates only when TFT set changes or OP.GG refreshes statistics (typically daily)","Play style classifications are OP.GG-defined categories; custom play style filters not supported","Augment recommendations are statistical aggregates, not contextual to current game state (player items, remaining units, etc.)","No real-time match data or in-progress game analysis — only historical meta statistics","Rank tier filtering may have sparse data at extreme ranks (Challenger) due to small sample sizes"],"requires":["Current TFT set identifier (e.g., 'Set 11') — OP.GG typically supports 1-2 active sets","Optional: rank tier filter (string: 'IRON', 'BRONZE', 'SILVER', 'GOLD', 'PLATINUM', 'DIAMOND', 'MASTER', 'CHALLENGER')","Optional: play style filter (string: 'aggressive', 'control', 'economy', or similar OP.GG-defined categories)","Optional: desired_output_fields to reduce response payload"],"input_types":["TFT set identifier (string)","Rank tier (string)","Play style category (string)","desired_output_fields (array of field names)"],"output_types":["Meta deck compositions (unit names, synergies, average placement, win rate)","Item build recommendations (optimal items, item combinations, synergy descriptions)","Augment data (augment names, tier, synergy effects, pick rates)","Play style classifications and tier-specific meta shifts"],"categories":["data-processing-analysis","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-op-gg__cap_3","uri":"capability://data.processing.analysis.valorant.agent.map.and.leaderboard.data.retrieval.with.region.specific.filtering","name":"valorant agent, map, and leaderboard data retrieval with region-specific filtering","description":"Exposes 6 tools for querying Valorant competitive data including agent statistics (pick rates, win rates, ban rates), map-specific meta, leaderboard rankings, and player match history. Tools are prefixed with 'valorant_' and support filtering by region (NA, EU, APAC, etc.) and rank tier to surface region-specific meta variations. Returns structured data about agent viability, map-specific strategies, and competitive player rankings.","intents":["Fetch current agent meta and pick/ban rates for a specific rank tier and region","Query map-specific agent recommendations and economy strategies","Look up player leaderboard rankings and recent match performance","Build region-aware AI agents that recommend agent selections based on local meta"],"best_for":["Valorant esports analysts and content creators covering regional competitive scenes","AI coaching agents providing agent selection recommendations during agent select phase","Competitive players researching region-specific meta before tournaments","Developers building Valorant companion apps with live meta data"],"limitations":["Region-specific data may have sparse samples at high ranks (Radiant/Immortal) due to small player pools","Agent meta updates reflect historical data (typically 24-48 hours old) rather than real-time pick rates","Map-specific strategies are statistical aggregates; no contextual recommendations based on team composition or opponent agents","Leaderboard data updates periodically (typically daily); real-time ranking changes not reflected immediately","No in-game economy data or round-by-round strategy information — only match-level aggregates"],"requires":["Region code (string: 'NA', 'EU', 'APAC', 'BR', 'LATAM', 'KR', 'JP') for region-specific queries","Optional: rank tier filter (string: 'IRON', 'BRONZE', 'SILVER', 'GOLD', 'PLATINUM', 'DIAMOND', 'ASCENDANT', 'IMMORTAL', 'RADIANT')","Optional: agent name for agent-specific analytics","Optional: map name for map-specific meta queries","Optional: desired_output_fields to reduce response payload"],"input_types":["Region code (string)","Rank tier (string)","Agent name (string)","Map name (string)","Player name/tag for leaderboard lookups","desired_output_fields (array of field names)"],"output_types":["Agent statistics (pick rate, ban rate, win rate, average combat score, average kills/deaths/assists)","Map-specific meta (agent viability per map, economy strategies, site-specific tactics)","Leaderboard rankings (player name, rank, rating points, recent match results)","Player match history (agents played, map, result, performance metrics)"],"categories":["data-processing-analysis","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-op-gg__cap_4","uri":"capability://data.processing.analysis.esports.schedule.and.tournament.data.aggregation.across.multiple.games","name":"esports schedule and tournament data aggregation across multiple games","description":"Aggregates esports schedule, team roster, and tournament data across League of Legends, Teamfight Tactics, and Valorant competitive scenes. Returns structured data about upcoming matches, team information, player rosters, tournament brackets, and historical match results. Supports filtering by game title, region, and tournament tier (e.g., regional leagues, international events). Data is updated periodically as tournaments progress.","intents":["Fetch upcoming esports match schedules and broadcast times for a specific region or game","Look up team rosters and player information for esports organizations","Query historical tournament results and match statistics for competitive analysis","Build esports content aggregators or Discord bots that announce upcoming matches"],"best_for":["Esports content platforms and news aggregators covering multiple gaming titles","Tournament organizers and esports teams tracking match schedules and results","AI agents generating esports match previews and predictions","Community Discord bots announcing upcoming esports matches"],"limitations":["Tournament data updates are periodic (typically daily or per-match-day) rather than real-time","Historical data availability varies by tournament tier; regional league data more complete than international events","No live match data (current score, round-by-round progression) — only pre-match and post-match information","Team roster data may lag behind official announcements by 24-48 hours","Broadcast time data may not account for timezone conversions; client responsible for localization"],"requires":["Game title filter (string: 'lol', 'tft', 'valorant') to specify which esports scene to query","Optional: region code (string: 'NA', 'EU', 'KR', 'CN', etc.) for region-specific tournaments","Optional: tournament tier filter (string: 'regional', 'international', 'challenger', etc.)","Optional: desired_output_fields to reduce response payload"],"input_types":["Game title (string)","Region code (string)","Tournament tier (string)","Team name or player name for roster lookups","desired_output_fields (array of field names)"],"output_types":["Match schedules (match ID, teams, scheduled time, region, tournament name)","Team rosters (team name, players, roles, organization)","Tournament brackets and standings (team rankings, win-loss records, points)","Historical match results (teams, final score, MVP, match statistics)"],"categories":["data-processing-analysis","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-op-gg__cap_5","uri":"capability://tool.use.integration.dynamic.mcp.capability.discovery.and.tool.registry.mirroring.at.startup","name":"dynamic mcp capability discovery and tool registry mirroring at startup","description":"At startup, the proxy fetches serverCapabilities from the remote OP.GG MCP endpoint and dynamically registers corresponding request/notification handlers on the local MCP Server. This enables the proxy to work with any remote MCP endpoint without hardcoding tool definitions. When the remote endpoint adds, removes, or modifies tools, the local proxy automatically reflects these changes on the next startup without code changes. Implementation reads capabilities once at initialization and conditionally registers handlers based on what the remote server advertises.","intents":["Support upstream tool changes without requiring proxy code modifications or redeployment","Enable the proxy to work with multiple remote MCP endpoints by dynamically discovering their capabilities","Reduce maintenance burden by eliminating hardcoded tool registries that must be manually synchronized with upstream"],"best_for":["Teams maintaining long-lived MCP proxies that need to adapt to upstream API changes","Builders creating generic MCP proxy infrastructure that should work with any remote endpoint","Developers who want to avoid manual tool registry synchronization between local and remote servers"],"limitations":["Capability discovery happens only at startup; tool changes on the remote endpoint require proxy restart to take effect","No caching of discovered capabilities; each startup incurs a network round-trip to fetch serverCapabilities","If the remote endpoint is unavailable at startup, the proxy fails to initialize (no graceful degradation with cached capabilities)","Dynamic capability discovery adds startup latency (typically 100-500ms for HTTP round-trip to remote endpoint)","Tool schema changes on the remote endpoint are not validated against local client expectations; schema mismatches may cause runtime errors"],"requires":["Network connectivity to remote MCP endpoint at startup time","Remote endpoint must implement MCP serverCapabilities protocol (standard MCP feature)","Node.js runtime with @modelcontextprotocol/sdk library for MCP protocol implementation"],"input_types":["Remote MCP endpoint URL (https://mcp-api.op.gg/mcp)","MCP serverCapabilities response (JSON structure describing available tools and their schemas)"],"output_types":["Registered request/notification handlers on local MCP Server","Tool definitions available to local MCP clients (automatically mirrored from remote)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-op-gg__cap_6","uri":"capability://data.processing.analysis.response.payload.optimization.via.field.level.filtering.at.api.boundary","name":"response payload optimization via field-level filtering at api boundary","description":"All 27 tools across League of Legends, Teamfight Tactics, and Valorant support a desired_output_fields parameter that filters response payloads at the remote API level. Clients specify which fields to include in the response (e.g., ['winRate', 'pickRate', 'banRate']), and the remote endpoint returns only those fields, reducing payload size and token consumption. This filtering happens server-side before the response is transmitted back through the proxy, minimizing bandwidth usage and LLM context overhead.","intents":["Reduce token consumption in LLM contexts by excluding unnecessary fields from API responses","Minimize network bandwidth usage when querying large datasets (e.g., full leaderboards)","Optimize response latency by reducing payload size transmitted over the network","Build efficient AI agents that only request the specific data fields needed for decision-making"],"best_for":["Token-constrained LLM applications where every byte of context matters","High-volume data aggregation scenarios where bandwidth optimization is critical","Mobile or edge deployments with limited network bandwidth","AI agents that need to minimize context window usage for cost or latency reasons"],"limitations":["Requires knowledge of available field names for each tool; no schema introspection or field discovery API","Field filtering is all-or-nothing; partial field selection not supported (either include a field or exclude it entirely)","No computed fields or field transformations; only raw fields returned by the remote API can be filtered","If desired_output_fields is omitted, the full response is returned (no default field set to minimize payload)","Field names are tool-specific; no standardized field naming across different tools"],"requires":["Knowledge of available field names for the specific tool being queried (documented in tool schemas)","Optional: desired_output_fields array parameter (if omitted, full response is returned)","Remote OP.GG endpoint must support field filtering (standard feature of all 27 tools)"],"input_types":["desired_output_fields (array of strings, e.g., ['winRate', 'pickRate', 'banRate'])"],"output_types":["Filtered JSON response containing only specified fields","Reduced payload size compared to full response"],"categories":["data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-op-gg__cap_7","uri":"capability://data.processing.analysis.multi.game.gaming.data.aggregation.under.unified.mcp.interface","name":"multi-game gaming data aggregation under unified mcp interface","description":"Consolidates gaming data from three distinct titles (League of Legends, Teamfight Tactics, Valorant) under a single MCP interface with 27 tools organized by game prefix (lol_, tft_, valorant_). Enables single MCP clients to query data across all three games without managing separate API integrations. Tools share common patterns (desired_output_fields filtering, region/tier filtering, structured response schemas) while maintaining game-specific data models and tool names.","intents":["Query gaming data across multiple titles from a single MCP client without separate integrations","Build multi-game content platforms that aggregate meta data, esports schedules, and player stats","Create AI agents that can provide recommendations across League, TFT, and Valorant ecosystems","Reduce integration complexity by consolidating three game APIs into one MCP interface"],"best_for":["Multi-game esports platforms and content aggregators","Gaming communities that span multiple titles (e.g., esports organizations with teams in multiple games)","AI agents providing cross-game recommendations or analysis","Developers building unified gaming dashboards covering multiple titles"],"limitations":["Tool naming requires game prefixes (lol_, tft_, valorant_) to avoid collisions; no unified tool naming across games","Data models are game-specific; no common schema for cross-game comparisons (e.g., 'win rate' definitions vary by game)","Meta data freshness may differ by game (League updates more frequently than TFT or Valorant)","Region support varies by game (League has more regions than Valorant); region codes not standardized across games","No cross-game analytics or comparative data (e.g., 'which game has the highest skill ceiling') — only game-specific data"],"requires":["MCP client capable of handling 27 tools with game-specific prefixes","Knowledge of which game's tools to query for specific use cases (lol_ for League, tft_ for TFT, valorant_ for Valorant)","Optional: region codes and rank tiers specific to each game"],"input_types":["Game-prefixed tool names (lol_*, tft_*, valorant_*)","Game-specific parameters (summoner names, agent names, deck compositions, etc.)"],"output_types":["Game-specific structured data (champion stats, agent meta, deck compositions, etc.)","Unified response format (JSON with desired_output_fields filtering applied)"],"categories":["data-processing-analysis","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-op-gg__cap_8","uri":"capability://tool.use.integration.streamable.http.client.transport.for.remote.mcp.endpoint.connectivity","name":"streamable http client transport for remote mcp endpoint connectivity","description":"Uses StreamableHTTPClientTransport from the @modelcontextprotocol/sdk library to establish HTTP connections to the remote OP.GG MCP endpoint at https://mcp-api.op.gg/mcp. This transport handles HTTP request/response serialization, error handling, and connection management for MCP protocol messages. Enables the local proxy to communicate with the remote endpoint over standard HTTP without custom HTTP client code, leveraging the SDK's built-in transport abstraction.","intents":["Connect to remote MCP endpoints over HTTP without implementing custom HTTP client logic","Leverage standard MCP protocol serialization and deserialization for HTTP communication","Handle HTTP connection lifecycle (connection pooling, error recovery, timeouts) automatically"],"best_for":["Builders creating MCP proxies that need to connect to remote HTTP-based MCP endpoints","Teams wanting to avoid custom HTTP client implementation and rely on standard MCP transport abstractions","Developers integrating MCP clients with remote services over HTTP"],"limitations":["StreamableHTTPClientTransport is a specific SDK implementation; switching to different HTTP libraries requires code changes","No built-in request caching or response memoization; each tool call results in a fresh HTTP request","HTTP connection pooling and timeout behavior depends on SDK defaults; limited customization options","No built-in retry logic or exponential backoff for failed requests; failures propagate immediately to the client","Streaming HTTP responses are supported but may add latency compared to non-streaming responses"],"requires":["@modelcontextprotocol/sdk library (version not specified, but latest recommended)","Node.js runtime with native fetch API or polyfill for HTTP requests","Network connectivity to remote MCP endpoint (https://mcp-api.op.gg/mcp)"],"input_types":["Remote endpoint URL (https://mcp-api.op.gg/mcp)","MCP protocol messages (JSON-RPC 2.0 format)"],"output_types":["MCP protocol responses (JSON-RPC 2.0 format over HTTP)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-op-gg__cap_9","uri":"capability://tool.use.integration.stdio.server.transport.for.local.mcp.client.communication","name":"stdio server transport for local mcp client communication","description":"Uses StdioServerTransport from the @modelcontextprotocol/sdk library to expose the local MCP Server over stdin/stdout to local MCP clients (Claude Desktop, Cursor, custom MCP clients). This transport handles JSON-RPC 2.0 message serialization over stdio, connection lifecycle management, and error handling. Enables the proxy to present itself as a standard MCP server to any stdio-based MCP client without custom protocol implementation.","intents":["Expose the local proxy as a standard MCP server to Claude Desktop and other stdio-based MCP clients","Handle JSON-RPC 2.0 message serialization and deserialization over stdin/stdout automatically","Manage stdio connection lifecycle (initialization, message handling, error recovery) without custom code"],"best_for":["Builders creating MCP servers that need to integrate with Claude Desktop or other stdio-based MCP clients","Teams wanting to avoid custom stdio protocol implementation and rely on standard MCP transport abstractions","Developers building MCP proxies that need to expose themselves as local servers"],"limitations":["StdioServerTransport is stdio-specific; switching to other transports (WebSocket, HTTP) requires code changes","Single-threaded stdio processing means concurrent requests from multiple clients will queue sequentially","No built-in request queueing or priority handling; all requests processed in FIFO order","Stdio buffering may introduce latency for high-frequency message exchanges","No built-in authentication or authorization; all local processes with stdio access can invoke tools"],"requires":["@modelcontextprotocol/sdk library (version not specified, but latest recommended)","Node.js runtime with stdio access (standard for Node.js processes)","MCP client supporting stdio transport (Claude Desktop, Cursor, or custom MCP client)"],"input_types":["JSON-RPC 2.0 messages over stdin from local MCP client"],"output_types":["JSON-RPC 2.0 messages over stdout to local MCP client"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":31,"verified":false,"data_access_risk":"high","permissions":["Node.js runtime (version not specified in docs, but dist/index.js implies Node 14+)","Network access to https://mcp-api.op.gg/mcp endpoint","MCP client supporting stdio transport (Claude Desktop, Cursor, or custom MCP client)","Optional: Smithery configuration file (smithery.yaml) for automated process spawning, or manual npm/npx invocation","Valid summoner name and region (e.g., 'NA', 'EUW', 'KR') for summoner-specific queries","Champion name or ID for champion-specific analytics","Optional: desired_output_fields array to specify which response fields to include (e.g., ['winRate', 'pickRate', 'banRate'])","For Smithery: Smithery client installed, smithery.yaml configuration file","For npm/npx: Node.js 14+ and npm, or npx (bundled with npm 5.2+)","For Docker: Docker runtime, Dockerfile (provided in repo), and Docker image build capability"],"failure_modes":["Adds network round-trip latency for every tool call (remote HTTP request to https://mcp-api.op.gg/mcp)","No local caching or request deduplication — each tool call results in a fresh HTTP request","Requires network connectivity to remote OP.GG endpoint; no offline fallback or graceful degradation","Single-threaded stdio processing means concurrent requests from multiple clients will queue sequentially","Data freshness depends on OP.GG's update frequency (typically 5-15 minute delay from live matches)","Summoner lookups require exact summoner name and region; fuzzy matching not supported","Match history limited to recent matches (typically last 100-200 matches); full historical data not available","Pro player and esports data may lag behind live events by several minutes","No real-time in-game data (current game state, live position tracking) — only completed match data","Smithery installation requires Smithery client and smithery.yaml configuration; not suitable for non-Smithery environments","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.47,"ecosystem":0.39999999999999997,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-06-17T09:51:03.579Z","last_scraped_at":"2026-05-03T14:00:15.503Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=op-gg","compare_url":"https://unfragile.ai/compare?artifact=op-gg"}},"signature":"44VQPRS6sQGwU7/dI69Ai/nP19VO7XUuSwv2mgQpc7U6EuP2Y0To1Dj2iE0LSeqAuP+mfDJ8NwAdyknO2IMYAw==","signedAt":"2026-06-21T18:45:56.263Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/op-gg","artifact":"https://unfragile.ai/op-gg","verify":"https://unfragile.ai/api/v1/verify?slug=op-gg","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}