FPL Context
PYPI · FPL-CONTEXT-MCP
Live Fantasy Premier League data for AI agents: fixtures, players, squads, injuries. No setup.
Available components
Last scanned (19 hours ago)
Scores higher than 63% of PyPI servers
Category Entertainment and Games
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security44
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Declares code that runs automatically (build-time code we could not rule out (a Hatch, PDM or setuptools build hook, a dynamic version we could not read statically, shipped VCS metadata or a stray root module)) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
- 0 of 31 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to sbanthia92/fpl-context-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1389 tokens (~138/item across 10 items; 9 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: the tool surface changed between 0.6.2 and 0.11.1: 2 tool removals, 0 breaking changes, 9 additions. See how to fix → Fail
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.11.0 → 0.11.1 functional
- 21 Oct 26 +15
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Tool coverage: 100% → 89% ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 466 → 142 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Schema quality: excellent → good functional
- Destructive annotations: 0 → pass functional
- Package version: 0.8.0 → 0.11.0 functional
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27.
- 18 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 17 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13.
- 14 Oct 26 +14
- Stability: unverified → fail ▼ security
- Malware scan: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- Schema quality: 755 → 466 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: good → excellent functional
- 12 Oct 26 −25
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.7.1 → 0.8.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Analysed pypi/fpl-context-mcp@0.11.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | sbanthia92/fpl-context-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/sbanthia92/fpl-context-mcp/.github/workflows/publish.yml@refs/tags/v0.11.1 |
| Rekor log index | 3378500317 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:e41603d28bd3e7fae608d4dc801f747df9b147381ffc5dc7210692770547a55f |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_hook | unreviewed | legacy backend root module |
Background: Why install scripts are a supply-chain risk →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_current_gameweek ~57
The current and next FPL gameweek and the transfer deadline, live from the FPL API. Use it to anchor 'this week' / 'next week' questions and to say how long a manager has left to make transfers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_fixture_run ~137
How easy or hard a team's next few fixtures are, live from the FPL API: average FDR (1 easiest, 5 hardest), home/away split, and blank or double gameweeks. Pass team for its fixture-by-fixture run; omit it to rank all 20 teams, easiest run first. Prefer this over get_fixtures when judging transfers, captaincy or chip timing.
| Name | Type | Req | Description |
|---|---|---|---|
| gameweeks | integer | – | Window length from the next gameweek (default 5). |
| team | string | – | Team name or short name, e.g. 'Arsenal', 'Man City' or 'MCI'. |
No output schema declared.
No examples provided.
get_fixtures ~150
FPL fixtures with difficulty ratings (FDR, 1 easiest to 5 hardest), live from the FPL API. With no arguments lists the next 5 gameweeks for every team. Pass team to see one team's run from its own point of view, gameweek for a single round, or gameweeks_ahead for a longer window.
| Name | Type | Req | Description |
|---|---|---|---|
| gameweek | integer | – | A single gameweek. Overrides gameweeks_ahead. |
| gameweeks_ahead | integer | – | Gameweeks to list from the next one to play (default 5). |
| team | string | – | Team name or short name, e.g. 'Arsenal', 'Man City' or 'MCI'. |
No output schema declared.
No examples provided.
get_gameweek_stats ~159
Every player's stats for one gameweek, ranked (default: the latest gameweek with results, sorted by points). Live from the FPL API. Use it for 'top scorers last week', 'which defenders kept clean sheets in GW9' or 'who got the most bonus'. Filter by position and team.
| Name | Type | Req | Description |
|---|---|---|---|
| gameweek | integer | – | Gameweek (default: the latest with results). |
| limit | integer | – | Rows to return (default 15). |
| position | string | – | – |
| sort_by | string | – | Stat to rank by, highest first (default total_points). |
| team | string | – | Team name or short name, e.g. 'Arsenal', 'Man City' or 'MCI'. |
No output schema declared.
No examples provided.
get_live_availability ~182
Current FPL injury, suspension and availability flags, fetched live from the FPL API. Call this before recommending, picking or captaining any player, so a newly flagged or suspended player isn't missed. With no arguments it lists every player who currently has a flag, newest news first. Pass player names to check specific players (returned even when fully available), and/or statuses to filter. Status codes: a available, d doubtful, i injured, s suspended, u unavailable (left club / on loan), n not in squad. chance_of_playing is FPL's estimate for the next round.
| Name | Type | Req | Description |
|---|---|---|---|
| players | array | – | Player names to look up, e.g. ['Saka', 'Haaland']. Case-insensitive; matches first, second or web name. |
| statuses | array | – | Only return players with these FPL status codes. |
No output schema declared.
No examples provided.
get_manager_squad ~128
A manager's FPL squad for a gameweek, with captain, bench, bank, squad value, transfers and the chips they have used, looked up by their FPL team ID (live from FPL's public API, no login needed). The team ID is the number in the URL of the manager's FPL Points page. Use it as the starting point for transfer, captain and chip advice on their actual team.
| Name | Type | Req | Description |
|---|---|---|---|
| gameweek | integer | – | Gameweek to show (default: the manager's current one). |
| team_id | integer | yes | FPL team ID. |
No output schema declared.
No examples provided.
get_player_history ~159
A player's match-by-match record this season (minutes, goals, assists, clean sheets, bonus, xG/xA, points), optionally only against one opponent or the last N matches, plus their season totals for past seasons. Live from the FPL API. Use it for 'how has Saka done against Spurs this season' or 'is his form real'. FPL provides match-level data for the current season only; past seasons are totals, so opponent splits for earlier seasons do not exist.
| Name | Type | Req | Description |
|---|---|---|---|
| last_n | integer | – | Only the most recent N matches. |
| opponent | string | – | Only matches against this team. |
| player | string | yes | Player name, e.g. 'Saka' or 'Bukayo Saka'. |
No output schema declared.
No examples provided.
get_xpts ~196
Rank players by estimated expected points (xPts) for a gameweek, live from the FPL API. A transparent baseline built from season xG/xA/clean-sheet/save/bonus rates, expected minutes, availability and fixture difficulty, shown beside FPL's own ep_next. Filter by position, team and max price. Good for captain shortlists and finding transfer targets; it is noisy early in the season and ignores rotation, so cross-check availability with get_live_availability.
| Name | Type | Req | Description |
|---|---|---|---|
| gameweek | integer | – | Gameweek to project (default: the next one to play). |
| limit | integer | – | Rows to return (default 15). |
| max_price | number | – | Maximum price in £m, e.g. 7.5. |
| position | string | – | – |
| team | string | – | Team name or short name, e.g. 'Arsenal', 'Man City' or 'MCI'. |
No output schema declared.
No examples provided.
search_players ~204
Find and rank current-season FPL players, live from the FPL API: by name, team, position and maximum price, sorted by a chosen stat. Returns price, total points, form, ownership, FPL's expected points for the next gameweek (ep_next) and availability status. Use it for 'best midfielders under £8m', 'how is Palmer doing', or to find a replacement.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows to return (default 15). |
| max_price | number | – | Maximum price in £m, e.g. 7.5. |
| name | string | – | Part of a first, second or web name, e.g. 'saka'. |
| position | string | – | – |
| sort_by | string | – | Stat to rank by, highest first (default total_points). |
| team | string | – | Team name or short name, e.g. 'Arsenal', 'Man City' or 'MCI'. |
No output schema declared.
No examples provided.
How do I install the FPL Context MCP server?
FPL Context runs locally as a PyPI package, launched with uvx fpl-context-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · fpl-context-mcp
claude mcp add sbanthia92-fpl-context-mcp -- uvx fpl-context-mcp
What is the FPL Context MCP server?
FPL Context is an MCP server listed in the public MCP registry as io.github.sbanthia92/fpl-context-mcp. Live Fantasy Premier League data for AI agents: fixtures, players, squads, injuries. No setup. This page covers its PyPI package (fpl-context-mcp).
Is the FPL Context MCP server safe to use?
FPL Context scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 October 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the FPL Context MCP server expose?
FPL Context exposes 9 tools: get_live_availability, get_current_gameweek, get_fixtures, search_players, get_manager_squad, and 4 more. Their descriptions and schemas cost roughly 1,372 tokens of context every time the server is loaded.
Is the FPL Context MCP server still maintained?
FPL Context is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the FPL Context MCP server under?
FPL Context declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.