SCRIPTMASTERLABS — ScriptDocs

by FastDrop

MCP MCP VERIFIED Verified yesterday Registry import free

Live npm, PyPI and crates.io package facts, READMEs and vulnerability checks for coding agents.

Live npm, PyPI and crates.io package facts, READMEs and vulnerability checks for coding agents. Official MCP Registry: com.scriptmasterlabs/scriptdocs@1.0.0. Remote endpoint: https://scriptdocs-mcp.onrender.com/mcp

Problem it solves

Discoverable MCP server listed in the official MCP Registry.

How it's different

Remote MCP endpoint ingested from the official registry and probed by FastDrop.

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as com.scriptmasterlabs/scriptdocs and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Claim this listing

Tools this endpoint exposes

Read directly from the endpoint on 29 Oct 2026. Not supplied by the maker.

docs_get_package_info
Fetch real, current metadata for a package directly from the npm registry, PyPI JSON API, or crates.io. This tool makes a live HTTP request to the actual registry (registry.npmjs.org, pypi.org, or cr
docs_get_readme
Fetch the real README/description for a package, straight from the registry — not a summary, not a paraphrase, not AI-generated. For npm this reads the registry's stored README, falling back to the p
docs_search_docs
Search for keywords inside a package's real README/docs and return verbatim matching snippets with surrounding context. This does keyword matching over the actual fetched document (registry README fo
docs_check_vulnerabilities
Check a real, specific package version against OSV.dev (Google-run, aggregates GitHub/PyPA/npm/RustSec advisories) — and, when a fix exists, automatically fetch that fixed version's README in the same
docs_resolve_library
Turn a fuzzy or partial name into real, ranked candidate package names, using the registry's own live search index — not a guess at what the package is probably called. For npm this queries registry.