No user-submitted related servers found.
Scored across 6 tools
Each tool maps to a distinct workflow step: name resolution, documentation lookup, migration guidance, manifest audit, single-package verdict, and batch-package verdict. The descriptions explicitly distinguish check-package from check-packages and clarify when find-library can be skipped because get-docs accepts registry-qualified ids directly.
All tools use kebab-case and mostly follow a verb_noun pattern (find-library, get-docs, check-manifest, check-package). The only minor deviation is upgrade-guide, which reads more like a noun compound, but overall the naming is predictable and readable.
Six tools is well-scoped for a package supply-chain and documentation server. Each tool has a clear role, and the batch check-packages tool prevents the count from being unnecessarily inflated by per-dependency checks.
The surface covers resolving package names, retrieving docs, planning upgrades, auditing lockfiles and GitHub workflows, and checking one or many packages for advisories. No obvious lifecycle step for supply-chain safety or package documentation is missing.
