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