Remote MCP · Endpoint

Form Guide MCP server

No. Form Guide answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://goodturn-mcp.pages.dev/formguide/mcp

The last check completed an MCP handshake.

Registry name
io.github.GoodTurnStudio/formguide
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
43 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Football form, fixtures, results and tables for six top European leagues.
Listing
From the official MCP registry (active).
Recent checks of Form Guide
CheckedResultHandshake
6 hours agoHandshake completed43 ms
9 days agoHandshake completed92 ms
10 days agoHandshake completed59 ms
11 days agoHandshake completed129 ms
12 days agoHandshake completed54 ms
14 days agoHandshake completed192 ms
15 days agoHandshake completed68 ms
15 days agoHandshake completed112 ms
17 days agoHandshake completed104 ms
19 days agoHandshake completed64 ms
22 days agoHandshake completed34 ms
24 days agoHandshake completed43 ms
26 days agoHandshake completed139 ms
28 days agoHandshake completed43 ms

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

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 Form Guide and makes no claim about it beyond what these checks measured.