Official PickADive MCP server — live dive-conditions, seasonality, and site data
Official PickADive MCP server — live dive-conditions, seasonality, and site data for AI agents. Free, read-only, hosted at pickadive.com/mcp
active Production-safe Score 85/100 http no auth
At a glance
| Endpoint | https://pickadive.com/mcp |
|---|---|
| Source | https://github.com/afiliptsov/pickadive-mcp |
| Transport | http |
| Tools | 5 |
| Auth | none |
| First seen | 2026-08-25 19:40:58 |
| Last checked | 2026-11-17 21:26:32 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 1405 / 1870 ms |
| Last successful check | 2026-11-17 21:26:32 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (5)
find_dive_windows— Ranked scuba-diving forecast windows near a place for a specific day. Answers "where can I dive near {place} on {day}?" with favorable and mspecies_seasonality— Month-by-month seasonality for marquee dive species from recorded GBIF sightings: peak month, regional season windows, and (optionally) thetop_dive_regions— Regions worldwide ranked by how many sites have a favorable dive-forecast window in the next ~72 hours, with per-region counts and links. Ansite_facts— Public facts for one named dive site: depths, difficulty, access (shore/boat), hazards, entry and exit notes, water type, and its page link.best_time_to_dive— Month-by-month climatology for ONE destination: the share of days historically favorable, typical water temperature and seas, plus marine-li
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:26:32 | ✓ | ✓ | 463 ms | 89 | active |
| 2026-11-17 20:42:23 | ✓ | ✓ | 1392 ms | 85 | active |
| 2026-11-17 19:57:37 | ✓ | ✓ | 1424 ms | 85 | active |
| 2026-11-17 19:29:10 | ✓ | ✓ | 1415 ms | 85 | active |
| 2026-11-17 18:56:43 | ✓ | ✓ | 627 ms | 89 | active |
| 2026-11-17 18:26:57 | ✓ | ✓ | 1359 ms | 85 | active |
| 2026-11-17 17:42:33 | ✓ | ✓ | 1374 ms | 85 | active |
| 2026-11-17 16:57:26 | ✓ | ✓ | 1322 ms | 85 | active |
| 2026-11-17 16:27:11 | ✓ | ✓ | 712 ms | 89 | active |
| 2026-11-17 15:40:54 | ✓ | ✓ | 1671 ms | 85 | active |
| 2026-11-17 14:55:25 | ✓ | ✓ | 1369 ms | 85 | active |
| 2026-11-17 14:25:14 | ✓ | ✓ | 747 ms | 89 | active |
| 2026-11-17 13:40:11 | ✓ | ✓ | 1435 ms | 85 | active |
| 2026-11-17 12:56:05 | ✓ | ✓ | 1489 ms | 85 | active |
| 2026-11-17 12:39:40 | ✓ | ✓ | 1447 ms | 85 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://pickadive.com/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/pickadive-com-mcp # JSON