Remote MCP · Endpoint

Form Guide MCP server

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

UpLast checked 10 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
10 hours agoHandshake completed43 ms
2 days agoHandshake completed139 ms
4 days agoHandshake completed43 ms
6 days agoHandshake completed80 ms
8 days agoHandshake completed74 ms
10 days agoHandshake completed79 ms
12 days agoHandshake completed80 ms
14 days agoHandshake completed47 ms
15 days agoHandshake completed15 ms
16 days agoHandshake completed23 ms
19 days agoHandshake completed14 ms
20 days agoHandshake completed22 ms
22 days agoHandshake completed17 ms
23 days agoHandshake completed21 ms

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

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.