mcp server
surf-trip-planner
Surf trip planner: live 0-100 Strike Scores, 10-day forecasts, and trip picks for 1,100+ spots.
Description as published by the maintainer. Source
- version 0.1.0
- active
active — Registry entry last updated 2026-07-03.
What this server can do
5 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
compare_surf_destinations(surferLevel, travelMonth, destinations)- Use this when a user is deciding between specific countries, regions, or surf spots. Compares Strike Mission fit by ability level, season, travel access, hazards, consistency, and recommended spot candidates. Required: destinations.
find_surf_trip_guides(query, intent)- Use this when the user wants surf trip planning guidance, such as landlocked surfer planning, where to surf next, avoiding flat trips, cheap surf flights, or Surfline alternatives.
get_live_spot_forecast(spot)- Use this when the user asks whether a specific surf spot is worth surfing or traveling to soon. Fetches the live 10-day Strike Mission forecast and best days for one spot. Required: spot.
get_spot_planning_context(spot)- Use this when the user asks about a specific surf spot. Returns difficulty, hazards, season, travel access, wave type, swell/wind requirements, and Strike Mission links. Required: spot.
recommend_surf_trip_destinations(budget, maxResults, surferLevel, travelMonth, originAirport, warmWaterOnly, avoidHeavyWaves, preferredRegions, includeBoatAccess, preferredCountries)- Use this when a user asks where to surf, where to fly for surf, how to plan a landlocked surfer trip, or which destinations fit their ability. Returns Strike Mission destination candidates with ability fit, season, travel, hazards, and dashboard links. For near-term trips (this month), candidates are ranked by live 10-day Strike Scores.
Last successful function declaration observed on . Source: https://www.strikemission.app/api/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://www.strikemission.app/api/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-03 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-03 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 5 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | www.strikemission.app | |
| mcp endpoint status | ok | The server listed 5 functions when asked. | as of probe | www.strikemission.app |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json