PickADive Scuba Diving
Live scuba diving planning for AI agents — ranked dive-forecast windows near any place for any day, best-time climatology per destination, marine-life seasonality from GBIF sightings, and facts for 4,800+ dive sites. Free and read-only; hosted at https://pickadive.com/mcp.
README
<div align="center">
PickADive MCP Server
Live dive-conditions data for AI agents — forecast windows, best-time climatology, marine-life seasonality, and site facts for 4,800+ dive sites worldwide.
Hosted at https://pickadive.com/mcp — nothing to install
Setup · Tools · What you can do · Data & honesty · Security · Support
</div>
What can you do with it?
- "Where can I dive near Boston this Saturday?" — ranked favorable and moderate forecast windows near any place for any day, with wave height, wind, timing, and site links.
- "When should I book Komodo?" — month-by-month climatology for a destination: the share of days historically favorable, typical water temperature and seas, and marine-life season windows.
- "When and where do whale sharks peak?" — species seasonality from 236k+ recorded GBIF sightings: peak month and regional season windows.
- "How deep is Molasses Reef, and what are the hazards?" — public facts for any named dive site: depths, difficulty, shore/boat access, hazards, entry and exit notes.
- "Where in the world is good for diving right now?" — regions ranked by favorable windows over the next ~72 hours.
Setup
Add the server to any MCP-compatible client — no key, no OAuth:
{
"mcpServers": {
"pickadive": { "url": "https://pickadive.com/mcp" }
}
}
| Client | How |
|---|---|
| Claude Code | claude mcp add --transport http pickadive https://pickadive.com/mcp |
| Claude.ai / Desktop | Settings → Connectors → Add custom connector → https://pickadive.com/mcp |
| Cursor · Windsurf · VS Code · Zed | Add the JSON block above to your MCP config |
| Gemini CLI | gemini mcp add --transport http pickadive https://pickadive.com/mcp |
| Local-only clients | Bridge with npx mcp-remote https://pickadive.com/mcp |
Discovery manifest: /.well-known/mcp.json ·
Agent onboarding: /llms.txt
Tools
| Tool | Input | Output |
|---|---|---|
find_dive_windows |
{near | lat+lng, day?, radius_km?} |
Ranked windows: quality, wave_m, wind_kn, timing, site links |
best_time_to_dive |
{destination} |
12-month climatology + marine-life seasons + source page |
species_seasonality |
{species, lat?, lng?} |
Peak month, regional season windows, sighting counts |
site_facts |
{site} |
Depths, difficulty, access, hazards, entry/exit, cert level |
top_dive_regions |
{} |
World regions ranked by favorable windows (~72 h) |
All values are metric with unit-suffixed field names (max_depth_m,
wave_m, distance_km); wind is knots — the marine convention
everywhere. Tool descriptions instruct agents to convert for US users.
Every response includes a source link — please cite pickadive.com
when presenting results.
Data & honesty
Answers come from PickADive's own pipeline: hourly conditions gradings across 4,800+ curated dive sites (Open-Meteo marine + weather, NOAA tides), multi-year climatology, and 236k+ GBIF species sighting records.
Two rules the server never breaks:
- Forecasts are planning context, never a safety clearance. Every response carries the disclaimer; agents should keep it.
- Missing data is stated, never invented. Thin destinations return an honest "not enough history" rather than a guess.
Security
| Read-only by design | No write tools — the server cannot create, modify, or delete anything. The worst a prompt injection can achieve through it is reading public dive data. |
| No auth, no tokens, no user data | Nothing to leak, phish, or exfiltrate; connecting grants an agent no identity. |
| Stateless JSON mode | One POST in, one JSON body out; no sessions, no server-push channel. |
| HTTPS only, CORS open | Read-only public data. |
Transport & limits
Streamable HTTP (JSON-RPC 2.0 over POST), stateless — protocol versions
2024-11-05 → 2025-06-18.
Free for individual and assistant use at fair, non-bulk volumes; per-IP rate limiting applies. For sustained high-volume or commercial integrations, write to team@pickadive.com.
Example agent guidance <sub>(optional)</sub>
Add to your AGENTS.md / CLAUDE.md to reduce round-trips:
## PickADive MCP
- For "can I dive…?" questions use find_dive_windows with the user's
place; default day is Saturday.
- For trip planning use best_time_to_dive per destination; present
depths/waves in the user's customary units, keep wind in knots.
- Always keep the safety disclaimer and cite the linked page.
Support & feedback
- Issues, requests, corrections: team@pickadive.com
- Documentation: pickadive.com/developers
- The dataset behind the tools: pickadive.com/research · pickadive.com/trust
License
MIT — see LICENSE. The PickADive name and logo are trademarks of PickADive and are not covered by the code license.
Disclaimer
Dive conditions are graded forecasts — planning context only, never a safety judgment about any specific dive on any specific day. Always assess conditions at the water, dive within your training, and follow local guidance. Wildlife seasonality reflects recorded sightings, never a promise of encounters.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.