Sailing Event Performance MCP

A public, no-auth MCP server for competitive sailing analysis — results, rank at every mark, per-leg speeds, what each tack and gybe cost, course geometry and wind bands. Built on the SAP Sailing Analytics public API.

https://sailing.sillsengineering.com/mcp

Data © SAP Sailing Analytics — sapsailing.com. This server reads SAP's public API and reshapes it for agents; it does not own the data. Every tool response repeats this attribution in its provenance block. If you show this data to a person, show the attribution with it.

Connect

Claude Code

claude mcp add --transport http --scope user sailing \
  https://sailing.sillsengineering.com/mcp

claude.ai or Claude Desktop

Settings → Connectors → Add custom connector, and paste the endpoint URL above. There is no sign-in step: the server takes no credentials from callers.

Any MCP client

Streamable HTTP — one POST with a JSON-RPC 2.0 body per request, no SSE.

curl -sS https://sailing.sillsengineering.com/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Tools

Call describe first. It states what the server can and cannot answer and how the tools chain — it is the grounding surface, not a brochure.

Tool	What it returns
`describe`	Capabilities, exclusions, conventions, and the workflow. Start here.
`find_events`	Regatta / event discovery across the tracked catalogue.
`get_event`	An event's races, plus its wind summary.
`get_results`	Leaderboard: ranks, net points, per-race scores including discards.
`get_race`	Race structure: start times, legs, course geometry, mark coordinates.
`get_race_performance`	Per-leg, per-competitor: average and max SOG, distance, tacks, gybes, penalties.
`get_maneuvers`	Detected tacks and gybes: entry/exit/lowest speed, turn angle, metres lost.
`analyze_race`	Composed race story: rank at every mark joined to per-leg and manoeuvre detail.

Chaining

find_events(query) → get_event(name) for its races → get_results / get_race / get_race_performance / get_maneuvers / analyze_race. The leaderboard name usually equals the regatta name.

Names are exact strings. Pass regatta and race names back exactly as the previous tool returned them — don't normalise or re-case them.

Conventions worth knowing

Wind is FROM degrees. SAP stores the direction wind blows to; this server converts to the nautical convention and says so in every response.
Missing stays missing. If SAP didn't publish a value it comes back null. Nothing is invented, interpolated or back-filled.
Provenance on every answer. Each response names its source and any conversion applied.

What this server does not have

No raw GPS tracks and no raw wind fixes. SAP gates those behind a permission this server does not hold. It is public-tier only, by design — so questions that need breadcrumb positions or individual wind samples cannot be answered here, and the server will tell you so rather than approximate.

Events SAP does not track are also unavailable.

Fair use

30 requests/min and 300 requests/hr per IP, plus a global ceiling. Over the limit returns 429 with Retry-After — please back off.
Please don't bulk-enumerate the catalogue. Ask for the events you actually want.
The server is also polite to its upstream: per-race detail is cached for 30 days (it doesn't change once a race is sailed), and outbound calls to SAP are rate-limited, concurrency-capped and circuit-broken. Repeat queries against a regatta you've already touched are effectively free; sweeping many new ones is not.

Status

GET /health returns liveness. Server manifest · llms.txt