SCRIPTMASTERLABS — ScriptDocs
Server Details
Live npm/PyPI/crates facts + README fetch for agents. Settle-proven 2026-11-02 (SELF-PROOF).
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 5 tools
Each tool has a distinct role in a clear pipeline: resolve a fuzzy name, fetch metadata, fetch the full README, search within docs, and check vulnerabilities. The only mild overlap is docs_get_readme vs docs_search_docs, since both ultimately pull the same registry document, but their output shapes (full text vs verbatim snippets) are clearly differentiated in the descriptions.
All five tools follow the exact same docs_verb_noun pattern (docs_check_vulnerabilities, docs_get_package_info, docs_get_readme, docs_resolve_library, docs_search_docs) with no stylistic deviations. The shared docs_ prefix also cleanly signals the server's domain.
Five tools is on the lean side but each one earns its place in the lookup workflow, with no redundant entries. It could reasonably add one or two more (e.g. version listing) without bloat, so it sits just under a perfect scope.
The surface covers a full read-only research lifecycle: disambiguate name → metadata → full docs → targeted keyword search → vulnerability check with fix docs. Notable gaps remain (no version enumeration, no dependency/changelog data, and PyPI resolution is explicitly unsupported), but agents can work around these using the existing tools.
Available Tools
5 toolsdocs_check_vulnerabilitiesCheck Package VulnerabilitiesARead-onlyIdempotentInspect
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 just a CVE list you have to research further yourself.
This is a live query against OSV.dev's public API for the exact package+version given. It never estimates or guesses risk — if OSV has no advisories on record for that version, this correctly reports zero vulnerabilities rather than implying danger that isn't documented. Note: this tool is more limited than dedicated vulnerability-intelligence tools (e.g. VulnCheck, Snyk) — it reports what OSV.dev has on file, not exploit activity or threat intelligence.
Args:
ecosystem ('npm' | 'pypi' | 'cargo')
package_name (string): exact package name
version (string, optional): specific version to check; defaults to the latest published version
include_fix_docs (boolean, default true): also fetch the README for the version that fixes the found vulnerabilities
Returns JSON with: vulnerability_count, vulnerabilities (array of {id, summary, severity, aliases, fixed_in, references}), recommended_fix (null, or {version, readme, truncated, source_url} for the version that resolves the found issues), source_url, fetched_at.
Error Handling:
Returns "Error: ..." if the package doesn't exist or OSV.dev can't be reached
vulnerability_count: 0 with an empty array is a normal, valid result — not an error
If fetching the fix's README fails, recommended_fix is null rather than the whole call failing — the vulnerability data itself is never withheld because of it [PAID: $0.009 per call via x402 - send a PAYMENT-SIGNATURE header on the /mcp request; unpaid calls return an HTTP 402 x402 challenge with five accepts at the same $0.009 price: Base USDC (9000 atomic), Solana USDC (9000 atomic), XRPL XRP (drops at the live XRP/USD rate), Arc USDC (9000 atomic), or Xahau XAH (drops at the live XAH/USD rate). The other ScriptDocs tools are free.]
Inputs: ecosystem (required), package_name (required), version, include_fix_docs.
docs_get_package_infoGet Package InfoARead-onlyIdempotentInspect
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 exist, it returns an explicit error rather than a plausible-looking fabrication.
Args:
ecosystem ('npm' | 'pypi' | 'cargo'): which registry to query
package_name (string): exact package name, e.g. "zod", "fastapi", or "serde"
Returns JSON with: name, latest_version, description, homepage, repository, source_url (the exact registry URL the data came from, for verification), fetched_at (ISO timestamp).
Error Handling:
Returns "Error: package not found" if the registry has no such package
Returns "Error: registry request failed" on network/HTTP errors
Inputs: ecosystem (required), package_name (required).
docs_get_readmeGet Package READMEARead-onlyIdempotentInspect
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 this reads the exact long_description shown on the package's PyPI page (verbatim). For Cargo (Rust/crates.io) this reads crates.io's stored README — note: crates.io only stores a pre-rendered HTML version, not the original markdown source, so this is that HTML converted to plain text, not byte-for-byte source.
Args:
ecosystem ('npm' | 'pypi' | 'cargo')
package_name (string): exact package name
version (string, optional): specific version; defaults to latest
Returns JSON with: readme (truncated to 12000 chars if longer — check 'truncated'), truncated (boolean), source_url (exact URL fetched, for verification), fetched_at.
Error Handling:
Returns "Error: ..." if the package or its README cannot be found — never fabricates content to fill the gap. [PAID: $0.009 per call via x402 - send a PAYMENT-SIGNATURE header on the /mcp request; unpaid calls return an HTTP 402 x402 challenge with five accepts at the same $0.009 price: Base USDC (9000 atomic), Solana USDC (9000 atomic), XRPL XRP (drops at the live XRP/USD rate), Arc USDC (9000 atomic), or Xahau XAH (drops at the live XAH/USD rate). The other ScriptDocs tools are free.]
Inputs: ecosystem (required), package_name (required), version.
docs_resolve_libraryResolve Library NameARead-onlyIdempotentInspect
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 search endpoint. For PyPI: there is currently no official PyPI search API (XML-RPC search was permanently disabled in 2022 and never replaced) — calling this with ecosystem 'pypi' returns an explicit message saying so rather than a fabricated or scraped result, along with a suggestion to use the exact package name with docs_get_package_info instead.
Args:
ecosystem ('npm' | 'pypi' | 'cargo')
query (string): the name or description to resolve, e.g. "react" or "async http client"
max_results (number, 1-10, default 5)
Returns JSON with: candidates (array of {name, version, description, score, url}), source_url, fetched_at.
Error Handling:
ecosystem 'pypi' always returns an explanatory message, not an error and not fabricated results
Returns "Error: ..." only for actual npm/crates.io request failures
Inputs: query (required), ecosystem (required), max_results.
docs_search_docsSearch Package DocsARead-onlyIdempotentInspect
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 paraphrase, and it does not answer from general knowledge. If no matches are found, it says so rather than guessing at an answer.
Args:
ecosystem ('npm' | 'pypi' | 'cargo')
package_name (string): exact package name
query (string): keyword(s) to search for, e.g. "rate limit" or "async client"
max_snippets (number, 1-20, default 5): cap on returned matches
version (string, optional): specific version to search; defaults to latest
Returns JSON with: snippets (array of {match, context, line_hint}), source_url, fetched_at.
Error Handling:
Returns "Error: ..." if the package/docs can't be fetched
Returns an empty snippets array (not an error) if the docs were fetched successfully but the query has no matches
Inputs: query (required), ecosystem (required), package_name (required), version, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Live npm and UNPKG data for AI agents: resolution, audits, import maps, malware/CVE checks.
npm & PyPI freshness for AI agents: latest version, deprecations, dated breaking-change diffs.
Real-time package and vulnerability data (Python, npm, Cargo, Go, and more) for AI coding agents.
Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.
Related MCP Servers
- AlicenseAqualityBmaintenanceVerified, dated facts for AI coding agents: what breaks between npm package versions (diffed from TypeScript types), per-version vulnerabilities, the newest version compatible with a given Node/Python/Rust/PHP, end-of-life dates of ~480 runtimes and frameworks, and AI model prices. Covers npm, PyPI, crates.io and Packagist.121AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents and developers to query NPM, PyPI, and Crates.io simultaneously for current stable versions, licenses, deprecation notices, runtime requirements, core dependencies, and install commands.MIT
- AlicenseAqualityBmaintenanceProvides software supply-chain intelligence for AI agents, enabling them to query package metadata, versions, downloads, dependencies, and health signals for npm, PyPI, and crates.io packages without API keys.666 npmMIT
- AlicenseNot gradedqualityBmaintenanceLive npm and UNPKG data for AI agents: package resolution, project audits, import maps, and malware/CVE checks. Optional Shield sign-in for domain data.1MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.