PickADive Scuba Diving
REMOTE · PICKADIVE.COM · SCANNED SEP 24
Live scuba dive planning: forecast windows, best-time climatology, species seasons, 4,800+ sites.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 854 tokens (~170/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the PickADive Scuba Diving MCP server?
PickADive Scuba Diving is a hosted endpoint at https://pickadive.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · pickadive.com
claude mcp add --transport http com-pickadive-mcp 'https://pickadive.com/mcp'
{
"mcpServers": {
"com-pickadive-mcp": {
"url": "https://pickadive.com/mcp"
}
}
} {
"servers": {
"com-pickadive-mcp": {
"type": "http",
"url": "https://pickadive.com/mcp"
}
}
} [mcp_servers.com-pickadive-mcp] url = "https://pickadive.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-pickadive-mcp": {
"type": "remote",
"url": "https://pickadive.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-pickadive-mcp --url 'https://pickadive.com/mcp' --transport streamable-http
mcp_servers:
com-pickadive-mcp:
url: "https://pickadive.com/mcp" {
"McpServers": {
"com-pickadive-mcp": {
"Transport": "http",
"Url": "https://pickadive.com/mcp"
}
}
} assistant mcp add com-pickadive-mcp -t streamable-http -u 'https://pickadive.com/mcp'
{
"mcpServers": {
"com-pickadive-mcp": {
"type": "http",
"url": "https://pickadive.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://pickadive.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pickadive.com | CN=YR2,O=Let's Encrypt,C=US | 11 Aug 2026 | 9 Nov 2026 | RSA 2048 | SHA256-RSA | 6367d9c5e0accf219ba2c01a2038563f168 |
| SANs: pickadive.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pickadive.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| pickadive.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pickadive.com/mcp | Verified | 200 | |
| http (plaintext) | http://pickadive.com/mcp | HTTPS enforced | 308 | https://pickadive.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
best_time_to_dive Best time of year to dive a destination ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | Country or famous destination name, e.g. "Bonaire", "Komodo", "Red Sea". |
No output schema declared.
No examples provided.
find_dive_windows Find dive windows near a place ~252
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. Forecast planning context only — never a safety clearance.
| Name | Type | Req | Description |
|---|---|---|---|
| day | string | – | today | tomorrow | mon | tue | wed | thu | fri | sat | sun | YYYY-MM-DD. Default sat. |
| lat | number | – | Latitude in decimal degrees (use with lng instead of near). |
| lng | number | – | Longitude in decimal degrees (use with lat instead of near). |
| near | string | – | Town, city, zip, or place name, e.g. "Miami" or "Gloucester, MA". Provide this OR lat+lng. |
| radius_km | number | – | Search radius in km (10–500, default 150; auto-widens once if empty). |
No output schema declared.
No examples provided.
site_facts Facts about a specific dive site ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | Site name or slug, e.g. "Molasses Reef" or "1000-steps-bq". |
No output schema declared.
No examples provided.
species_seasonality When and where a marine species peaks ~168
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | – | Optional latitude — adds the season window for the region containing this point. |
| lng | number | – | Optional longitude. |
| species | string | yes | Species slug or common name, e.g. "humpback-whale" or "whale shark". |
No output schema declared.
No examples provided.
top_dive_regions Regions with the best dive windows right now ~47
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?".
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the PickADive Scuba Diving MCP server?
PickADive Scuba Diving is an MCP server listed in the public MCP registry as com.pickadive/mcp. Live scuba dive planning: forecast windows, best-time climatology, species seasons, 4,800+ sites. This page covers its hosted endpoint (https://pickadive.com/mcp).
Is the PickADive Scuba Diving MCP server safe to use?
PickADive Scuba Diving scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the PickADive Scuba Diving MCP server expose?
PickADive Scuba Diving exposes 5 tools: find_dive_windows, species_seasonality, top_dive_regions, site_facts, best_time_to_dive. Their descriptions and schemas cost roughly 741 tokens of context every time the server is loaded.
Does the PickADive Scuba Diving MCP server require authentication?
No. We connected to PickADive Scuba Diving without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PickADive Scuba Diving MCP server still maintained?
PickADive Scuba Diving is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.