Is the Pickadive MCP server down?

mcp-registry/com.pickadive/mcp · v1.1.0

As of 2026-10-25 03:21 UTC, the Pickadive MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 6 minutes.

Live scuba dive planning: forecast windows, best-time climatology, species seasons, 4,800+ sites.

claude mcp add --transport http pickadive-mcp-server https://pickadive.com/mcp

{
  "mcpServers": {
    "pickadive-mcp-server": {
      "type": "http",
      "url": "https://pickadive.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (84/100)

What to fix (3)

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.pickadive%2Fmcp/fixes

{
  "name": "find_dive_windows",
  "description": "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",
  "inputSchema": {
    "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)."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Find dive windows near a place"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.pickadive/mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.pickadive/mcp"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~991 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 100.00% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• find_dive_windows ~326 tokens
• species_seasonality ~229 tokens
• best_time_to_dive ~209 tokens
• site_facts ~122 tokens
• top_dive_regions ~105 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.pickadive%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fcom.pickadive%2Fmcp?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fcom.pickadive%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.pickadive%2Fmcp.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.pickadive%2Fmcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.pickadive%2Fmcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:30496e96170d5128…, first seen 2026-10-17, included at leaf 1923 of 63,566. Version history · verify what your client received.

Tools (5)

• best_time_to_dive
• find_dive_windows
• site_facts
• species_seasonality
• top_dive_regions

Compare: most reliable data servers · most reliable search servers · most reliable retrieval servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Pickadive MCP server down right now?

As of 2026-10-25 03:21 UTC, the Pickadive MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 6 minutes.

How many tools does Pickadive MCP server provide?

Pickadive MCP server advertises 5 tools, including best_time_to_dive, find_dive_windows, site_facts, species_seasonality, top_dive_regions.

How do I install Pickadive MCP server?

Point your MCP client at this streamable-http endpoint: https://pickadive.com/mcp

Is the Pickadive MCP server safe to connect to an AI agent?

Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Pickadive MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.