← Back to skills↗↗↗
Coding & devtools · Developer Tools · mcp
Package Documentation MCP
Integrates with multiple package registries and documentation sources to provide up-to-date library information for code assistance, dependency analysis, and learning about new libraries.
Overall score
71
mcpnodedeveloper toolsregistry validated
Setup difficulty
Easy
Install method
npm · local
Supported providers
Any provider
Supported hosts
MCP-compatible host
Permission posture
high
Last verified
Apr 10, 2026
Score breakdown
Utility80
Compatibility61
Ease of setup88
Reliability68
Docs quality73
Adoption60
Safety & maintenance50
Scores combine benchmark signals, product experience, and editorial weighting. Use them as a practical guide, not an absolute truth claim.
Best for
CodingAgent automation
Works with
MCP-compatible hostscommunity registry validated
Capabilities
Fetch Url DocsFetch Package DocsFetch Library DocsFetch Multilingual Docs
Sources & trust
Verified registry fields
SummaryRepository
This entry is live under the scaled catalog policy: maintainer repo + community registry metadata are visible, but VerdictLens did not treat it as fully official-field verified.
Package Documentation MCP repo
GitHub · Tier 4 · Apr 10, 2026
Repository
Awesome MCP Registry listing
Community registry · Tier 3 · Apr 10, 2026
SummaryDescriptionSubcategoryInstall methodCapabilities
Package Documentation MCP VerdictLens scale review
Manual review · Tier 3 · Apr 10, 2026
Best-fit guidanceWorks-with guidancePermission postureOverall score
Strengths
- Clear MCP-server-shaped capability boundary from a maintainer-controlled repository and structured registry entry.
- Imported from a community registry entry marked as validated/runnable, so it clears a higher live-catalog bar than generic discovery-only listings.
Things to watch
- VerdictLens has not manually reviewed every operational claim for this entry; trust the repo and source links more than the editorial score.
- Community validation is still weaker than direct official-document verification, so production teams should inspect permissions and install instructions before rollout.