Koskamo

PickADive MCP

An official MCP server operated by PickADive that provides scuba diving discovery and planning capabilities. It enables agents to access dive site data, forecast windows, species seasonality, and regional rankings to assist divers in planning trips and understanding marine conditions.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

PickADive MCP logo, by PickADiveVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by PickADive
MCP endpoint (Streamable HTTP)
https://pickadive.com/mcp
Vendor documentation

What its tools do

5 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

5 of 5 have a description · 0 of 5 declare behavior hints · 4 of 4 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to pickadive.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Find dive windows for a specific location and day
  • Check species seasonality and peak months
  • Identify top dive regions currently
  • Retrieve facts about specific dive sites

Source and maintenance

Vendor evidenceRegistry 1.1.0
Maintenance checked

Protocol and capabilities

Server
pickadive 1.1.0
MCP protocol negotiated in check
2025-06-18
Tools
5 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Read-only scuba-dive planning tools from pickadive.com: forecast windows near a place for a day, species seasonality from recorded GBIF sightings, and the world's best dive regions right now. All values are metric with unit-suffixed field names; present depths, waves, and distances in the user's customary units (US users: feet and miles), keeping wind in knots. Forecast-based planning context, never a safety clearance. Conditions must be verified locally, on the day, before any dive. Cite pickadive.com when presenting results.

Tools

5 advertised

find_dive_windows — Find dive windows near a place
Advertised by the server during the last successful anonymous check.

Ranked scuba-diving forecast windows near a place for a specific day. Answers "where can I dive near {place} on {day}?" with favorable and moderate windows (wave height, wind, timing) plus site links. Values are metric with unit-suffixed fields (max_depth_m, wave_m, distance_km; wind_kn is knots — the marine convention everywhere). When presenting to a user who uses US customary units, convert depths and waves to feet and distances to miles. computed_at is when the forecast behind the answer was generated (the oldest site in the answer) — quote the citation field verbatim (it carries that time); if stale is true, say the forecast has not been updated since then. Forecast planning context only — never a safety clearance.

find_dive_windows input schema
{
  "type": "object",
  "properties": {
    "day": {
      "type": "string",
      "description": "today | tomorrow | mon | tue | wed | thu | fri | sat | sun | YYYY-MM-DD. Default sat."
    },
    "lat": {
      "type": "number",
      "description": "Latitude in decimal degrees (use with lng instead of near)."
    },
    "lng": {
      "type": "number",
      "description": "Longitude in decimal degrees (use with lat instead of near)."
    },
    "near": {
      "type": "string",
      "description": "Town, city, zip, or place name, e.g. \"Miami\" or \"Gloucester, MA\". Provide this OR lat+lng."
    },
    "radius_km": {
      "type": "number",
      "description": "Search radius in km (10–500, default 150; auto-widens once if empty)."
    }
  }
}
species_seasonality — When and where a marine species peaks
Advertised by the server during the last successful anonymous check.

Month-by-month seasonality for marquee dive species from recorded GBIF sightings: peak month, regional season windows, and (optionally) the season at a specific point. Species available: whale-shark, scalloped-hammerhead, giant-manta, mola-mola, orca, humpback-whale, green-sea-turtle, tiger-shark, great-white-shark, reef-manta, thresher-shark, bull-shark. Recorded sightings, never a promise of encounters.

species_seasonality input schema
{
  "type": "object",
  "required": [
    "species"
  ],
  "properties": {
    "lat": {
      "type": "number",
      "description": "Optional latitude — adds the season window for the region containing this point."
    },
    "lng": {
      "type": "number",
      "description": "Optional longitude."
    },
    "species": {
      "type": "string",
      "description": "Species slug or common name, e.g. \"humpback-whale\" or \"whale shark\"."
    }
  }
}
top_dive_regions — Regions with the best dive windows right now
Advertised by the server during the last successful anonymous check.

Regions worldwide ranked by favorable dive-forecast windows over the next ~72 hours, with per-region counts and links. Answers "where in the world is good for diving this weekend?". computed_at is when the forecast behind the counts was generated; quote the citation field verbatim.

top_dive_regions input schema
{
  "type": "object",
  "properties": {}
}
site_facts — Facts about a specific dive site
Advertised by the server during the last successful anonymous check.

Public facts for one named dive site: depths, difficulty, access (shore/boat), hazards, entry and exit notes, water type, and its page link. Look up by site name or slug. Metric with unit-suffixed fields; convert for US users.

site_facts input schema
{
  "type": "object",
  "required": [
    "site"
  ],
  "properties": {
    "site": {
      "type": "string",
      "description": "Site name or slug, e.g. \"Molasses Reef\" or \"1000-steps-bq\"."
    }
  }
}
best_time_to_dive — Best time of year to dive a destination
Advertised by the server during the last successful anonymous check.

Month-by-month climatology for ONE destination: the share of days historically favorable, typical water temperature and seas, plus marine-life season windows. Accepts a country (e.g. "Bonaire", "Egypt") or a famous destination (Komodo, Raja Ampat, Nusa Penida, Socorro (Revillagigedo), Cozumel, Similan Islands, Koh Tao, Sipadan, Malapascua, Tubbataha, Galápagos, Red Sea, Great Barrier Reef, Sea of Cortez, Cocos Island, Lembeh Strait, Bunaken, Anilao, Amed & Tulamben). Historical patterns, never a forecast. Cite the linked page.

best_time_to_dive input schema
{
  "type": "object",
  "required": [
    "destination"
  ],
  "properties": {
    "destination": {
      "type": "string",
      "description": "Country or famous destination name, e.g. \"Bonaire\", \"Komodo\", \"Red Sea\"."
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
725 ms
95th percentile latency
725 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 725 ms · metadata changed · 5 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http pickadive-mcp https://pickadive.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add pickadive-mcp --url https://pickadive.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable pickadive-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "pickadive-mcp": {
      "url": "https://pickadive.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "pickadive-mcp": {
      "type": "streamableHttp",
      "url": "https://pickadive.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start pickadive-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "pickadive-mcp": {
      "type": "http",
      "url": "https://pickadive.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http pickadive-mcp https://pickadive.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://pickadive.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "pickadive-mcp": {
      "serverUrl": "https://pickadive.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like PickADive MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run PickADive MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing