ScriptDocs MCP Server
Related Servers
Alternatives to ScriptDocs MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseDqualityDmaintenanceA Model Context Protocol server that allows AI models to fetch detailed information about npm packages and discover popular packages in the npm ecosystem.112 npm1ISC
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides tools to fetch live, version-accurate documentation, changelogs, examples, and method signatures for npm and PyPI packages, preventing AI coding agents from hallucinating stale APIs.11 npmISC
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server for querying package registries (npm, PyPI, crates.io) to retrieve metadata, release timelines, and maintenance signals.1-
- AlicenseNot gradedqualityAmaintenanceA Model Context Protocol (MCP) server that scrapes, indexes, and searches documentation for third-party software libraries and packages, supporting versioning and hybrid search.1,449 npm1,768MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables AI agents to access, search, and understand structured package documentation and source code from Git repositories. It automatically generates specialized tools to browse module overviews, components, and detailed documentation for technical libraries.1698 npm7MIT
- AlicenseAqualityBmaintenanceAn MCP server that gives AI coding agents accurate, version-aware API documentation for any npm package — straight from the source.123 npmMIT
TDQS
Scored across 5 tools
Each tool has a clear, non-overlapping purpose: resolving names, fetching metadata, retrieving READMEs, searching within docs, and checking vulnerabilities. No two tools could be easily confused.
All tools share the docs_ prefix and follow a consistent verb_noun pattern (check, get, get, search, resolve). The naming is uniform and predictable.
Five tools is well-scoped for a focused documentation server covering metadata, README, search, name resolution, and vulnerability checks. Each tool earns its place with no redundancy.
The server covers the full workflow: resolving package names, fetching package info and READMEs, searching within docs, and checking vulnerabilities with fix documentation. No obvious gaps for the stated purpose.