feat: wire MCP server dead-code and impact tools to dedicated API endpoints

[jonathanpopham]

Context

The MCP server (internal/mcp/server.go) has inline implementations of findDeadFunctions and findAffected that do naive graph traversal (same approach the CLI commands used before #23 and #25). Now that client.DeadCode() and client.Impact() exist, the MCP tools should use them.

Current state

• dead_code MCP tool: inline graph edge counting (checks calls/contains_call edges)
• blast_radius MCP tool: inline reverse BFS on imports edges

Proposed change

• dead_code tool → call client.DeadCode(), return rich results (confidence, line, reason)
• blast_radius tool → call client.Impact(), return risk scores, affected files, entry points

Dependencies

• feat: wire dead-code to /v1/analysis/dead-code endpoint #23 client.DeadCode() ✅ merged
• feat: wire blast-radius to /v1/analysis/impact endpoint #25 client.Impact() (pending merge)

Notes

• VSA: changes are isolated to internal/mcp/server.go
• The MCP tool schemas (inputSchema) will need updating to expose new params (min_confidence, limit, diff)

[coderabbitai]

🔗 Related PRs

#23 - feat: wire dead-code to /v1/analysis/dead-code endpoint [closed]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!