Strike Mission MCP server

Which servers in the official MCP registry are Strike Mission's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-14

← Back to Strike Mission

Whose server it is

Registry nameapp.strikemission/surf-trip-plannerverified in the MCP registry

The registry name sits under strikemission.app. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-14

Stateanswerschecked 2026-10-14
Tools5
Server calls itselfstrike-mission-surf-trip-planner
Server version0.1.0
Protocol version2025-06-18

On 2026-10-14 the server answered initialize and tools/list without a sign-in. First answer in 826 ms.

Tools it offers5 tools · read 2026-10-14

recommend_surf_trip_destinations
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…
compare_surf_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.
get_spot_planning_context
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.
get_live_spot_forecast
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.
find_surf_trip_guides
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.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "surf-trip-planner": {
      "type": "http",
      "url": "https://www.strikemission.app/api/mcp"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.