MCP servers observed by Lowdown
app.strikemission/surf-trip-planner MCP server: daily status and tool changes
Answered initialize and tools/list on all 21 daily checks recorded in the last 30 days (2026-10-29 to 2026-11-18); 5 tools listed. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-29; no tool definition change in 19 compared days; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.strikemission/surf-trip-planner
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.strikemission/surf-trip-planner?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 21
- Answered initialize and tools/list: 21
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 21 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 19 compared days.
What tools does it list?
5 tools on 2026-11-18:
compare_surf_destinationsfind_surf_trip_guidesget_live_spot_forecastget_spot_planning_contextrecommend_surf_trip_destinations
MCP Registry declaration
- Registry name:
app.strikemission/surf-trip-planner - Declared version: 0.1.0
- Status: active
- Declared hosts:
www.strikemission.app
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:app.strikemission/surf-trip-planner", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.strikemission/surf-trip-planner?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).