check_team — DiveTripPlanner MCP Tool Read-only
check_team
(check team) is one of 6 tools on the
DiveTripPlanner
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_team from your client
- Claude Code DiveTripPlanner check_team run in your project directory
- Claude Desktop DiveTripPlanner check_team ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor DiveTripPlanner check_team ~/.cursor/mcp.json
- VS Code DiveTripPlanner check_team .vscode/mcp.json
- Zed DiveTripPlanner check_team ~/.config/zed/settings.json
- Windsurf DiveTripPlanner check_team ~/.codeium/windsurf/mcp_config.json
- Cline DiveTripPlanner check_team ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI DiveTripPlanner check_team ~/.gemini/settings.json
- Grok DiveTripPlanner check_team .mcp.json (in your project root)
- ChatGPT DiveTripPlanner check_team Settings → Connectors → Advanced → Developer mode
- Claude.ai DiveTripPlanner check_team Settings → Connectors → Add custom connector
- LangChain DiveTripPlanner check_team pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http caves https://divetripplanner.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 8 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.