Dep Scope
Audit npm imports at symbol level and get keep/replace/migrate verdicts before you ship or refactor dependencies.
Overview
io.github.FlorianBruniaux/dep-scope is a MCP server for the Ship phase that performs symbol-level npm dependency analysis with verdicts, native alternatives, and migration prompts.
What is this MCP server?
- Symbol-level npm dependency scans with explicit verdicts per usage
- Suggests native or lighter alternatives where applicable
- Migration-oriented prompts to guide incremental dependency removal
- stdio MCP via npx @florianbruniaux/dep-scope (dep-scope-mcp)
- Packaged as npm @florianbruniaux/dep-scope v0.4.2
- Server schema version 0.4.2
- npm package @florianbruniaux/dep-scope with stdio transport
- Runtime hint: npx with dep-scope-mcp entry
Community signal: 17 GitHub stars.
What problem does it solve?
You cannot tell from package.json alone which npm deps your code truly needs or what to drop without risky guesswork.
Who is it for?
Solo builders maintaining Node or TypeScript apps who want agent-driven dependency audits tied to real imports.
Skip if: Teams that only need a one-time license report with no symbol-level usage context or non-JavaScript stacks.
What do I get? / Deliverables
Your agent returns per-symbol dependency verdicts and migration guidance you can apply in focused refactors before shipping.
- Scan verdicts per dependency or symbol usage
- Native or lighter alternative recommendations
- Migration prompts suitable for agent-led refactors
Recommended MCP Servers
Journey fit
Dependency risk review belongs on the Ship shelf because it informs release readiness and bundle decisions, not greenfield feature work. Review subphase covers pre-release audits of what your codebase actually pulls from node_modules versus native APIs.
How it compares
MCP integration for dependency forensics, not a standalone CLI-only audit script you run outside the agent.
Common Questions / FAQ
Who is io.github.FlorianBruniaux/dep-scope for?
It is for indie and solo developers shipping npm-based apps who want their AI coding agent to analyze which dependencies matter at the symbol level.
When should I use io.github.FlorianBruniaux/dep-scope?
Use it during Ship-phase review when trimming bloat, evaluating native replacements, or planning migrations before a release.
How do I add io.github.FlorianBruniaux/dep-scope to my agent?
Register the MCP server with stdio and npx, passing --package @florianbruniaux/dep-scope and the dep-scope-mcp positional as in the server manifest.