scan_dependency — Kentucky Code MCP Tool
scan_dependency
(scan dependency) is one of 38 tools on the
Kentucky Code
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call scan_dependency from your client
- Claude Code Kentucky Code scan_dependency run in your project directory
- Claude Desktop Kentucky Code scan_dependency ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Kentucky Code scan_dependency ~/.cursor/mcp.json
- VS Code Kentucky Code scan_dependency .vscode/mcp.json
- Zed Kentucky Code scan_dependency ~/.config/zed/settings.json
- Windsurf Kentucky Code scan_dependency ~/.codeium/windsurf/mcp_config.json
- Cline Kentucky Code scan_dependency ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Kentucky Code scan_dependency ~/.gemini/settings.json
- Grok Kentucky Code scan_dependency .mcp.json (in your project root)
- ChatGPT Kentucky Code scan_dependency Settings → Connectors → Advanced → Developer mode
- Claude.ai Kentucky Code scan_dependency Settings → Connectors → Add custom connector
- LangChain Kentucky Code scan_dependency pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http kentucky-code https://gateway.pipeworx.io/kentucky-code/mcpOther tools on this server
- ask_pipeworx
- ask_pipeworx_beta
- ask_pipeworx_grounded
- search_within
- deep_research
- discover_tools
- resolve_entity
- compare_entities
- subscribe
- unsubscribe
- list_subscriptions
- recent_alerts
- entity_profile
- recent_changes
- validate_claim
- company_facts
- bet_research
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- polymarket_edge_tracker
- kalshi_weather_edge
- resolution_audit
- resolution_diff
- release_calendar_markets
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- forget
- ky_statute
- ky_search
This list was read from the server itself, by connecting to it and calling tools/list on 7 October 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.