Surf trip planner: live 0-100 Strike Scores, 10-day forecasts, and trip picks for 1,100+ spots.
Otherv0.1.0streamable-httpwww.strikemission.app
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 942ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo strike-mission-surf-trip-planner@0.1.0 |
| tooling | 35 / 35 | tools/list OK: 5 tools e.g. "recommend_surf_trip_destinations"; 5/5 described, 5/5 fully-typed schemas, median description 180 chars |
| latency | 7 / 10 | initialize round-trip 942ms |
| provenance | 12 / 15 | description present; no repository URL; version 0.1.0; namespace app.strikemission matches endpoint/repo |
Score 94/100 · latency 942ms · 5 tools · auth: open
Claude Code:
claude mcp add --transport http surf-trip-planner https://www.strikemission.app/api/mcp
Generic MCP client config:
{ "mcpServers": { "surf-trip-planner": { "type": "http", "url": "https://www.strikemission.app/api/mcp" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/app.strikemission/surf-trip-planner · referral link https://mcpqueen.com/go/app.strikemission/surf-trip-planner (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/app.strikemission/surf-trip-planner)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-12 19:18 | A | 94 | 942ms |