run_check — onboarding checklist inspection runs MCP Tool Mutating
run_check
(run check) is one of 16 tools on the
onboarding checklist inspection runs
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call run_check from your client
- Claude Code onboarding checklist inspection runs run_check run in your project directory
- Claude Desktop onboarding checklist inspection runs run_check ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor onboarding checklist inspection runs run_check ~/.cursor/mcp.json
- VS Code onboarding checklist inspection runs run_check .vscode/mcp.json
- Zed onboarding checklist inspection runs run_check ~/.config/zed/settings.json
- Windsurf onboarding checklist inspection runs run_check ~/.codeium/windsurf/mcp_config.json
- Cline onboarding checklist inspection runs run_check ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI onboarding checklist inspection runs run_check ~/.gemini/settings.json
- Grok onboarding checklist inspection runs run_check .mcp.json (in your project root)
- ChatGPT onboarding checklist inspection runs run_check Settings → Connectors → Advanced → Developer mode
- Claude.ai onboarding checklist inspection runs run_check Settings → Connectors → Add custom connector
- LangChain onboarding checklist inspection runs run_check pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http onboarding-checklist-inspection-runs https://mcp.zovo.one/mcp/onboarding-checklist-inspection-runsOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.