verify_dependency_change — RepoPilot MCP Tool
verify_dependency_change
(verify dependency change) is one of 8 tools on the
RepoPilot
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call verify_dependency_change from your client
- Claude Code RepoPilot verify_dependency_change run in your project directory
- Claude Desktop RepoPilot verify_dependency_change ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor RepoPilot verify_dependency_change ~/.cursor/mcp.json
- VS Code RepoPilot verify_dependency_change .vscode/mcp.json
- Zed RepoPilot verify_dependency_change ~/.config/zed/settings.json
- Windsurf RepoPilot verify_dependency_change ~/.codeium/windsurf/mcp_config.json
- Cline RepoPilot verify_dependency_change ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI RepoPilot verify_dependency_change ~/.gemini/settings.json
- Grok RepoPilot verify_dependency_change .mcp.json (in your project root)
- ChatGPT RepoPilot verify_dependency_change Settings → Connectors → Advanced → Developer mode
- Claude.ai RepoPilot verify_dependency_change Settings → Connectors → Add custom connector
- LangChain RepoPilot verify_dependency_change pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http repopilot https://repopilot.app/api/mcpOther 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.