# ScriptDocs MCP (npm · @scriptmasterlabs/scriptdocs-mcp-server)

Real, live npm/PyPI docs and OSV.dev vulnerability data for AI coding agents. No fake data.

- Trust score: 66/100 (medium)
- Change this week: +24
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `@scriptmasterlabs/scriptdocs-mcp-server`: 66/100 (this document), [markdown](https://verifymcp.io/servers/timwal78-scriptdocs-mcp-server/scriptmasterlabs-scriptdocs-mcp-server.md), [page](https://verifymcp.io/servers/timwal78-scriptdocs-mcp-server/scriptmasterlabs-scriptdocs-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@scriptmasterlabs/scriptdocs-mcp-server`
- Version: `0.3.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (122 of 124), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (122 of 124), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 10 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1794 tokens (~358/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add timwal78-scriptdocs-mcp-server -- npx -y @scriptmasterlabs/scriptdocs-mcp-server
```

### Codex

```bash
codex mcp add timwal78-scriptdocs-mcp-server -- npx -y @scriptmasterlabs/scriptdocs-mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "timwal78-scriptdocs-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@scriptmasterlabs/scriptdocs-mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add timwal78-scriptdocs-mcp-server --command npx --arg -y --arg @scriptmasterlabs/scriptdocs-mcp-server
```

### Hermes

```yaml
mcp_servers:
  timwal78-scriptdocs-mcp-server:
    command: "npx"
    args: ["-y", "@scriptmasterlabs/scriptdocs-mcp-server"]
```

### Other

```json
{
  "mcpServers": {
    "timwal78-scriptdocs-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@scriptmasterlabs/scriptdocs-mcp-server"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 65, +45)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [functional regression] Security disclosure: fail → unverified
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.23
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional] Licence: MIT

### 2026-08-01 (score 20, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-07-31 (score 5, −37)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-27 (score 42)

First indexed and scored.

## MCP tools (5)

### `docs_get_package_info` (~274 tokens)

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 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

Input parameters:

- `ecosystem` (string, required): Which package registry to query: 'npm', 'pypi', or 'cargo' (Rust/crates.io).
- `package_name` (string, required): Exact package name as published on the registry, e.g. 'express', 'requests', or 'serde'.

### `docs_get_readme` (~315 tokens)

Get Package 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 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.

Input parameters:

- `ecosystem` (string, required): Which package registry to query: 'npm', 'pypi', or 'cargo'.
- `package_name` (string, required): Exact package name as published on the registry.
- `version` (string): Specific version to fetch. Defaults to the latest published version if omitted.

### `docs_search_docs` (~351 tokens)

Search Package 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 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

Input parameters:

- `ecosystem` (string, required): Which package registry to query: 'npm', 'pypi', or 'cargo'.
- `max_snippets` (integer): Maximum number of matching snippets to return.
- `package_name` (string, required): Exact package name as published on the registry.
- `query` (string, required): Keyword(s) to search for inside the package's real documentation, e.g. 'authentication middleware'.
- `version` (string): Specific version to search within. Defaults to the latest published version if omitted.

### `docs_check_vulnerabilities` (~501 tokens)

Check Package 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 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

Input parameters:

- `ecosystem` (string, required): Which package registry the version belongs to: 'npm', 'pypi', or 'cargo'.
- `include_fix_docs` (boolean): When a vulnerability is found with a known fixed version, also fetch that version's README so the response includes what upgrading actually looks like. Set false to skip the extra fetch.
- `package_name` (string, required): Exact package name as published on the registry.
- `version` (string): Specific version to check. Defaults to the current latest published version if omitted.

### `docs_resolve_library` (~353 tokens)

Resolve Library Name

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

Input parameters:

- `ecosystem` (string, required): Which registry to search: 'npm', 'pypi', or 'cargo'. Note: PyPI has no official search API (see limitation below).
- `max_results` (integer): Maximum number of candidates to return.
- `query` (string, required): Natural-language or partial name to resolve, e.g. 'react', 'http client for python', 'serde'.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/timwal78-scriptdocs-mcp-server/scriptmasterlabs-scriptdocs-mcp-server#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 65
- 2026-08-01: 20
- 2026-07-31: 5
- 2026-07-30: 42
- 2026-07-28: 42
- 2026-07-27: 42

## Links

- npm package: https://www.npmjs.com/package/@scriptmasterlabs/scriptdocs-mcp-server
- Socket report: https://socket.dev/npm/package/@scriptmasterlabs/scriptdocs-mcp-server
- Repository: https://github.com/Timwal78/scriptdocs-mcp-server
- Website: https://scriptmasterlabs.com/
- Changelog RSS feed: https://verifymcp.io/servers/timwal78-scriptdocs-mcp-server/scriptmasterlabs-scriptdocs-mcp-server/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/timwal78-scriptdocs-mcp-server/scriptmasterlabs-scriptdocs-mcp-server/changelog.json
- HTML version of this page: https://verifymcp.io/servers/timwal78-scriptdocs-mcp-server/scriptmasterlabs-scriptdocs-mcp-server