Surf Trip Planner MCP server
{
"mcpServers": {
"strikemission-surf-trip-planner": {
"type": "http",
"url": "https://www.strikemission.app/api/mcp"
}
}
}{
"mcpServers": {
"strikemission-surf-trip-planner": {
"type": "http",
"url": "https://www.strikemission.app/api/mcp"
}
}
}{
"mcpServers": {
"strikemission-surf-trip-planner": {
"type": "http",
"url": "https://www.strikemission.app/api/mcp"
}
}
}{
"servers": {
"strikemission-surf-trip-planner": {
"type": "http",
"url": "https://www.strikemission.app/api/mcp"
}
}
}{
"mcpServers": {
"strikemission-surf-trip-planner": {
"type": "http",
"url": "https://www.strikemission.app/api/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 0.1.0
Surf trip planner: live 0-100 Strike Scores, 10-day forecasts, and trip picks for 1,100+ spots.
This entry comes from the registry but points to no public repository, so there is nothing to check: no commit history, no source, no tool list. It is listed for completeness and left out of search engines.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.
This server has not seen a commit in unknown. It may still work, but nobody is currently fixing it — check the alternatives before you build on it.