scan_dependency — Core Research MCP Tool
scan_dependency
(scan dependency) is one of 38 tools on the
Core Research
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 Core Research scan_dependency run in your project directory
- Claude Desktop Core Research scan_dependency ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Core Research scan_dependency ~/.cursor/mcp.json
- VS Code Core Research scan_dependency .vscode/mcp.json
- Zed Core Research scan_dependency ~/.config/zed/settings.json
- Windsurf Core Research scan_dependency ~/.codeium/windsurf/mcp_config.json
- Cline Core Research scan_dependency ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Core Research scan_dependency ~/.gemini/settings.json
- Grok Core Research scan_dependency .mcp.json (in your project root)
- ChatGPT Core Research scan_dependency Settings → Connectors → Advanced → Developer mode
- Claude.ai Core Research scan_dependency Settings → Connectors → Add custom connector
- LangChain Core Research scan_dependency pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http core-research https://gateway.pipeworx.io/core-research/mcp
Other 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
- search_papers
- get_paper
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.