Machine readers · MCP
GPSail as a tool.
The SailGP season on this site is available to AI assistants as a read-only Model Context Protocol server. An assistant that connects to it can read the season schedule, find the next race, and quote the current standings, with a source URL and a generation timestamp on every answer.
Endpoint
https://mcp.gpsail.net/mcp
gpsail.net is a static site, so its server runs as a small separate service on its own subdomain. Streamable HTTP, stateless: JSON-RPC 2.0 over POST with Accept: application/json, text/event-stream. No authentication, no accounts, read-only. In Claude: Settings, Connectors, add custom connector, paste the URL. In Claude Code: claude mcp add --transport http gpsail https://mcp.gpsail.net/mcp.
Tools
| Tool | What it returns |
|---|---|
gpsail_schedule | Every event in the season: venue, dates, status (upcoming, live, completed), winner when known, event URL. |
gpsail_next_race | The next upcoming event. Most events publish a day rather than a start time; the result says which, and never invents a clock time. Pass an IANA timezone to localize real timestamps. |
gpsail_standings | Current championship standings: position, team, points, and the timestamp they were generated, so an assistant can say how fresh they are. |
The data behind it
The same rows the pages render, published as JSON on every deploy: /data/schedule.json and /data/standings.json. Agents that prefer a file to a protocol can read those directly.
Three things to ask
- "When is the next SailGP race, and where?"
- "Who is leading the SailGP season right now, and how fresh is that?"
- "List the remaining SailGP events this season with their dates."
Privacy
The server keeps no accounts and retains nothing from a conversation. Requests are logged the way page requests are, as described in the privacy note.