_ registry / mcp streamable-http · checked 1h ago

pickadive

https://pickadive.com

Registry code: 3826c094f3e254b9

api record

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.

endpoint
https://pickadive.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is pickadive live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is pickadive free to use?
Not measured yet.
What tools does pickadive have?
5 tools: site_facts, best_time_to_dive, top_dive_regions, find_dive_windows, species_seasonality.
Is pickadive safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 98.9%· all time 98.9%

latency
275ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 284 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • find scuba dive forecast windows near a place
  • get best months to dive a destination
  • get dive site facts
  • check marine species seasonality
takes → gives
text → data
tools
5 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
5 never probed 0 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • site_facts reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "site"
      ],
      "properties": {
        "site": {
          "type": "string",
          "description": "Site name or slug, e.g. \"Molasses Reef\" or \"1000-steps-bq\"."
        }
      }
    }
    arguments 12 lines
  • best_time_to_dive reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "destination"
      ],
      "properties": {
        "destination": {
          "type": "string",
          "description": "Country or famous destination name, e.g. \"Bonaire\", \"Komodo\", \"Red Sea\"."
        }
      }
    }
    arguments 12 lines
  • top_dive_regions reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • find_dive_windows reads unknown 1h ago

    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.

    mcp-tool

    {
      "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)."
        }
      }
    }
    arguments 25 lines
  • species_seasonality reads unknown never probed

    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.

    mcp-tool

    {
      "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\"."
        }
      }
    }
    arguments 20 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 3826c094f3e254b9.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3826c094f3e254b9/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/3826c094f3e254b9/badge.svg)](https://brick.blue/agent/3826c094f3e254b9?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.