League Analysis MCP Server

league-analysis-mcp-server PyPI v0.3.1

Published by ari1110 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Model Context Protocol server for Yahoo Fantasy Sports API with advanced historical analysis and manager profiling

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

high Shell/command execution in server code (src/league_analysis_mcp_server/oauth_callback_server.py)MTC-SRC-002

In the server's implementation (`src/league_analysis_mcp_server/oauth_callback_server.py:230`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ] subprocess.run(cmd, check=True, capture_output=True, text=True) return cert_file, k

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/league_analysis_mcp_server/oauth_callback_server.py

Tools 60

Each tool and what it can reach — statically extracted from the published source.

  • analyze_draft_strategy_toolno sensitive capability
  • analyze_manager_historyno sensitive capability
  • check_setup_statusno sensitive capability
  • clear_cacheno sensitive capability
  • compare_seasonsno sensitive capability
  • create_yahoo_appno sensitive capability
  • evaluate_manager_skill_toolno sensitive capability
  • get_all_yahoo_fantasy_game_keysno sensitive capability
  • get_current_game_infono sensitive capability
  • get_current_game_metadatano sensitive capability
Show 50 more tools ↓
  • get_current_userno sensitive capability
  • get_enhanced_draft_resultsno sensitive capability
  • get_game_info_by_game_idno sensitive capability
  • get_game_key_by_seasonno sensitive capability
  • get_game_metadata_by_game_idno sensitive capability
  • get_game_position_types_by_game_idno sensitive capability
  • get_game_roster_positions_by_game_idno sensitive capability
  • get_game_stat_categories_by_game_idno sensitive capability
  • get_game_weeks_by_game_idno sensitive capability
  • get_historical_draftsno sensitive capability
  • get_league_draft_resultsno sensitive capability
  • get_league_infono sensitive capability
  • get_league_keyno sensitive capability
  • get_league_metadatano sensitive capability
  • get_league_playersno sensitive capability
  • get_league_scoreboard_by_weekno sensitive capability
  • get_league_settingsno sensitive capability
  • get_matchupsno sensitive capability
  • get_player_draft_analysisno sensitive capability
  • get_player_ownershipno sensitive capability
  • get_player_percent_owned_by_weekno sensitive capability
  • get_player_stats_by_dateno sensitive capability
  • get_player_stats_by_weekno sensitive capability
  • get_player_stats_for_seasonno sensitive capability
  • get_responseno sensitive capability
  • get_season_transactionsno sensitive capability
  • get_server_infono sensitive capability
  • get_setup_instructionsno sensitive capability
  • get_standingsno sensitive capability
  • get_team_draft_resultsno sensitive capability
  • get_team_infono sensitive capability
  • get_team_matchupsno sensitive capability
  • get_team_metadatano sensitive capability
  • get_team_rosterno sensitive capability
  • get_team_roster_player_info_by_dateno sensitive capability
  • get_team_roster_player_info_by_weekno sensitive capability
  • get_team_roster_player_statsno sensitive capability
  • get_team_roster_player_stats_by_weekno sensitive capability
  • get_team_standingsno sensitive capability
  • get_team_statsno sensitive capability
  • get_team_stats_by_weekno sensitive capability
  • get_user_gamesno sensitive capability
  • get_user_leaguesno sensitive capability
  • get_user_teamsno sensitive capability
  • list_available_seasonsno sensitive capability
  • predict_trade_likelihood_toolno sensitive capability
  • refresh_yahoo_tokenno sensitive capability
  • reset_authenticationno sensitive capability
  • save_yahoo_credentialsno sensitive capability
  • start_automated_oauth_flowno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.3.1 latest A 93/100 1 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/league-analysis-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/league-analysis-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/league-analysis-mcp-server"><img src="https://mcptrustchecker.com/registry/league-analysis-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/league-analysis-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan league-analysis-mcp-server --online --registry pypi

Use the free API → How scoring works

More in Gaming & Entertainment