com.scriptmasterlabs/scriptdocs · v1.0.0 · developer-tools
SCRIPTMASTERLABS — ScriptDocs is healthy: it completed an MCP handshake in 1147 ms and exposes 5 tools.
Live npm, PyPI and crates.io package facts, READMEs and vulnerability checks for coding agents.
Endpoint: https://scriptdocs-mcp.onrender.com/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 5 |
| Latency | 1147 ms |
| Last checked (UTC) | 2026-10-29T06:50:24.105Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-29T06:50:24.105Z | Healthy | 1147 |
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 crates.io) at call time. It never returns cached, guessed, or simulated data — if the package doesn't |
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 published README.md file via jsDelivr if the registry copy is missing (verbatim markdown). For PyPI t |
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 for npm, long description for PyPI, README-derived text for Cargo) — it does not summarize or paraphra |
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 call, so the result is "here's what's wrong" AND "here's exactly what upgrading looks like," not ju |
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.npmjs.org's actual search API (the same one npmjs.com uses). For Cargo this queries crates.io's real |