Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

app.strikemission/surf-trip-planner

REMOTE · WWW.STRIKEMISSION.APP · SCANNED SEP 21

Surf trip planner: live 0-100 Strike Scores, 10-day forecasts, and trip picks for 1,100+ spots.

0 this week 89 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability83
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 714 tokens (~119/item across 6 items; 5 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Install

How do I install the app.strikemission/surf-trip-planner MCP server?

app.strikemission/surf-trip-planner is a hosted endpoint at https://www.strikemission.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.strikemission.app

# add to Claude Code
claude mcp add --transport http app-strikemission-surf-trip-planner 'https://www.strikemission.app/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "app-strikemission-surf-trip-planner": {
      "url": "https://www.strikemission.app/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "app-strikemission-surf-trip-planner": {
      "type": "http",
      "url": "https://www.strikemission.app/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.app-strikemission-surf-trip-planner]
url = "https://www.strikemission.app/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-strikemission-surf-trip-planner": {
      "type": "remote",
      "url": "https://www.strikemission.app/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add app-strikemission-surf-trip-planner --url 'https://www.strikemission.app/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  app-strikemission-surf-trip-planner:
    url: "https://www.strikemission.app/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "app-strikemission-surf-trip-planner": {
      "Transport": "http",
      "Url": "https://www.strikemission.app/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add app-strikemission-surf-trip-planner -t streamable-http -u 'https://www.strikemission.app/api/mcp'
// mcp.json
{
  "mcpServers": {
    "app-strikemission-surf-trip-planner": {
      "type": "http",
      "url": "https://www.strikemission.app/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +1
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Probed https://www.strikemission.app/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.strikemission.app CN=YR2,O=Let's Encrypt,C=US 21 Jul 2026 19 Oct 2026 RSA 2048 SHA256-RSA 5cd74075767c3f09df5cca53bd8886b7dfa
SANs: www.strikemission.app
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.strikemission.app. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
strikemission.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(self)

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.strikemission.app/api/mcp Verified 200
http (plaintext) http://www.strikemission.app/api/mcp HTTPS enforced 308 https://www.strikemission.app/api/mcp
MCP tools · 5 exposed · ~657 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare_surf_destinations ~119

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.

NameTypeReqDescription
destinationsarrayyesCountries, regions, or spot names to compare, for example Mexico, Costa Rica, Portugal, Bali, Uluwatu.
surferLevelstringUser ability level.
travelMonthintegerTarget travel month from 1 to 12. Omit to use the current month.

No output schema declared.

No examples provided.

find_surf_trip_guides ~79

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.

NameTypeReqDescription
intentstringThe surf trip planning intent.
querystringOptional free-form user query to match against guide titles and keywords.

No output schema declared.

No examples provided.

get_live_spot_forecast ~81

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.

NameTypeReqDescription
spotstringyesSpot name, slug, or numeric Strike Mission spot id, for example Uluwatu, uluwatu, or 1.

No output schema declared.

No examples provided.

get_spot_planning_context ~80

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.

NameTypeReqDescription
spotstringyesSpot name, slug, or numeric Strike Mission spot id, for example Uluwatu, uluwatu, or 1.

No output schema declared.

No examples provided.

recommend_surf_trip_destinations ~298

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.

NameTypeReqDescription
avoidHeavyWavesbooleanSet true for beginners, intermediates, family trips, or anyone avoiding serious reef/slab conditions.
budgetstringBudget preference for the trip.
includeBoatAccessbooleanSet true if boat-only waves are acceptable.
maxResultsintegerMaximum number of recommendations.
originAirportstringOptional IATA origin airport, for example DEN, LAX, JFK, LHR, SYD.
preferredCountriesarrayOptional countries to prefer, for example Mexico, Costa Rica, Portugal.
preferredRegionsarrayOptional regions to prefer, for example Central America, Europe, Pacific, Southeast Asia.
surferLevelstringUser ability level. Use intermediate when the user can catch green waves and go down the line.
travelMonthintegerTarget travel month from 1 to 12. Omit to use the current month.
warmWaterOnlybooleanSet true when the user wants warm-water or boardshort-friendly surf.

No output schema declared.

No examples provided.

Common questions

What is the app.strikemission/surf-trip-planner MCP server?

app.strikemission/surf-trip-planner is an MCP server listed in the public MCP registry as app.strikemission/surf-trip-planner. Surf trip planner: live 0-100 Strike Scores, 10-day forecasts, and trip picks for 1,100+ spots. This page covers its hosted endpoint (https://www.strikemission.app/api/mcp).

Is the app.strikemission/surf-trip-planner MCP server safe to use?

app.strikemission/surf-trip-planner scores 89 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the app.strikemission/surf-trip-planner MCP server expose?

app.strikemission/surf-trip-planner exposes 5 tools: recommend_surf_trip_destinations, compare_surf_destinations, get_spot_planning_context, get_live_spot_forecast, find_surf_trip_guides. Their descriptions and schemas cost roughly 657 tokens of context every time the server is loaded.

Does the app.strikemission/surf-trip-planner MCP server require authentication?

No. We connected to app.strikemission/surf-trip-planner without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the app.strikemission/surf-trip-planner MCP server still maintained?

app.strikemission/surf-trip-planner is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.