Home / MCP registry index / com.fplcopilot/fpl-copilot
FPL Copilot
com.fplcopilot/fpl-copilot in the official MCP registry.
Endpoint https://api.fplcopilot.com/mcp.
The registry describes it as: Fantasy Premier League expected points, team ratings, captaincy and mini-league win chances.
We read its 21 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
rate_my_team get_my_team get_captain_picks find_players get_player compare_players get_fixture_ticker get_price_changes get_penalty_takers get_best_chip_squad get_mini_league get_mini_league_odds get_gameweek_review get_deadline get_predicted_lineups search_guides read_guide create_share_link get_player_breakdown get_player_breakdowns get_manager_squad
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-fplcopilot-fpl-copilot)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.