
Dep Scope
Scans your TypeScript/JavaScript project and tells you which npm packages can be replaced with native APIs, which are barely used, and which overlap with other libraries. Exposes five MCP tools: scan_project runs a full dependency audit with verdicts (KEEP, RECODE_NATIVE, REMOVE), analyze_package breaks down symbol-level usage for a single dependency, get_migration_candidates surfaces refactoring opportunities, generate_migration_prompt builds LLM-ready context for removing a package, and find_duplicates spots redundant libraries. Automatically checks config files like vitest.config and next.config to avoid false positives. Pairs well with Knip for unused detection. Reach for this when you inherit a bloated project or want to modernize dependencies without manually tracing every import.
- tools
- 5
- transport
- STDIO
- last updated
- May 5, 2026
Tools
5 toolsPublic tool metadata for what this MCP can expose to an agent.
scan_projectFull dependency scan with verdicts
Full dependency scan with verdicts
No parameter schema in public metadata yet.
analyze_packageSymbol-level breakdown of one package
Symbol-level breakdown of one package
No parameter schema in public metadata yet.
get_migration_candidatesList all RECODE_NATIVE + CONSOLIDATE packages
List all RECODE_NATIVE + CONSOLIDATE packages
No parameter schema in public metadata yet.
generate_migration_promptGenerate a migration prompt inline
Generate a migration prompt inline
No parameter schema in public metadata yet.
find_duplicatesDetect overlapping libraries
Detect overlapping libraries
No parameter schema in public metadata yet.
Sponsors
Readme
dep-scope
|
Florian BRUNIAUX · AI Founding Engineer @ Méthode Aristote 13 years from developer to CTO / VP Eng · Blog ↗ · Projects ↗ |
Details
- Repository
- github.com/florianbruniaux/node-dep-scope
- Package
@florianbruniaux/dep-scope- Transport
- STDIO
- Registry
- MCP registry, active
