Home / MCP registry index / com.getbeachfinder/beachfinder
BeachFinder - beaches and live conditions
com.getbeachfinder/beachfinder in the official MCP registry.
Endpoint https://getbeachfinder.com/mcp. Source: github.com/troulin-a11y/BeachFinder-mcp.
The registry describes it as: Search 184,900 swim spots, conditions, water activities, providers and guides worldwide.
We read its 12 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
search_beaches search_swim_spots search_surf_spots search_dive_snorkel_spots search_river_whitewater_spots search_vanlife_spots search_activity_providers search_guides get_spot_details get_spot_conditions get_community_conditions compare_spots
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-getbeachfinder-beachfinder)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.