Remote MCP · Endpoint

FPL Copilot MCP server

No. FPL Copilot answered an MCP handshake 16 minutes ago.

UpLast checked 16 minutes ago

Server URL

https://api.fplcopilot.com/mcp

The last check completed an MCP handshake.

Registry name
com.fplcopilot/fpl-copilot
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
283 ms
Tools exposed
21 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Fantasy Premier League expected points, team ratings, captaincy and mini-league win chances.
Listing
From the official MCP registry (active).
Recent checks of FPL Copilot
CheckedResultHandshake
16 minutes agoHandshake completed283 ms
8 days agoHandshake completed375 ms
9 days agoHandshake completed261 ms
11 days agoHandshake completed271 ms
12 days agoHandshake completed815 ms
13 days agoHandshake completed290 ms
14 days agoHandshake completed467 ms
14 days agoHandshake completed255 ms
16 days agoHandshake completed263 ms
19 days agoHandshake completed255 ms
21 days agoHandshake completed582 ms
24 days agoHandshake completed637 ms
26 days agoHandshake completed258 ms
28 days agoHandshake completed256 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 23 responding of 24.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with FPL Copilot and makes no claim about it beyond what these checks measured.