Home / MCP registry index / app.divekit/mcp
Dive Kit
app.divekit/mcp in the official MCP registry.
Endpoint https://mcp.divekit.app/mcp.
The registry describes it as: Experimental. Plan scuba decompression dives, gas blends and gas use with Dive Kit. Reference only.
We read its 18 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
plan_dive find_max_bottom_time check_no_deco read_share_link gas_specs best_mix get_guide lookup_cylinders lookup_certifications convert_units gas_usage mix_result plan_blend blend_continuous decant rmv_sac buoyancy_check lookup_references
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/app-divekit-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.