Dive Kit
MCP server · api.divekit.app · found in a public list · checked since 2026-11-01
Live, handshake completed · latest check
https://api.divekit.app/mcp MCP endpoint (Streamable HTTP)The name is the registry's label, not ours. Not reviewed by a person. See 2 endpoints from divekit.app.
Our checks
An unpaid request daily, from eastern North AmericaLast 1 checks, oldest to newest; room for 29 more
1 passed, 0 failed, 29 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hourssince 2026-11-01 | 1 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-11-01 | 1 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-11-01 | 1 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Tools listed by the server
best_mixblend_continuousbuoyancy_checkcheck_no_decoconvert_unitsdecantfind_max_bottom_timegas_specsgas_usageget_guidelookup_certificationslookup_cylinderslookup_referencesmix_resultplan_blendplan_diveread_share_linkrmv_sac
- Tools
- 18
- This list since
- 2026-11-01
- First listed to us
- 2026-11-01
- List changes, 90 days
- 0
Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions
Access
- Our latest check
- Nothing asked
- Stated
- not stated
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Interface it declares
- Protocol
- MCP 2025-06-18
- Capabilities
- tools
- Transports
- streamable-http
As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions
Calls it declares
plan_dive plan_name audience units response_format mode levels* descent_gas cylinders* gradient_factors stops environment rates ppo2 gas_consumption reserve → units summary table_markdown bailout_table_markdown stopsfind_max_bottom_time plan_name audience units mode levels* descent_gas cylinders* gradient_factors stops environment rates ppo2 gas_consumption reserve gas_switch → units kind limit level_number planned_mincheck_no_deco units depth* bottom_time_min oxygen_pct helium_pct gradient_factors water altitude previous_share_url surface_interval_min → units depth mix no_stop_minutes gfread_share_link url* units → plan_input plan_name has_tissue_state app_version results_summarygas_specs units oxygen_pct* helium_pct depth ppo2_max water temperature altitude o2_narcotic → units notation mod mod_1_4_bar min_depthbest_mix units depth* ppo2_max target_end water temperature altitude style → units depth best_mix standard_mix deco_ladderget_guide topic* → topic markdownlookup_cylinders query material units → dataset_version attribution cylinderslookup_certifications query agency category id → dataset_version attribution agency total_matches certificationsconvert_units quantity* value* from* to* cylinder_size → quantity value from to resultgas_usage units preset cylinder_size rated_pressure twinset start_pressure sac segments* reserve water altitude → units water cylinder sac segmentsmix_result units current* additions* environment → units start steps settle final
From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.
Listing
In the capability tree: Other (not placed in a branch yet) (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-11-01. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/6): ✗ what it does is unclear to our placement; ✓ its latest check passed.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:MIA |
Live, handshake completed HTTP 200 | 367 ms |
What these figures do not show
- A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
- Limited evidence: monitored for under 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_28aff9fcb7ca4d12