# SCRIPTMASTERLABS — ScriptDocs (remote · scriptdocs-mcp.onrender.com)

Live npm/PyPI/crates facts + README fetch for agents. Settle-proven 2026-11-02 (SELF-PROOF).

- Trust score: 73/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `scriptdocs-mcp.onrender.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-scriptmasterlabs-scriptdocs/scriptdocs-mcp.md), [page](https://verifymcp.io/servers/com-scriptmasterlabs-scriptdocs/scriptdocs-mcp)

## Channel facts

- Endpoint: `https://scriptdocs-mcp.onrender.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2015 tokens (~403/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**: 23/100
  - Stability observed for 7 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the SCRIPTMASTERLABS — ScriptDocs MCP server?

SCRIPTMASTERLABS — ScriptDocs is a hosted endpoint at https://scriptdocs-mcp.onrender.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-scriptmasterlabs-scriptdocs 'https://scriptdocs-mcp.onrender.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-scriptmasterlabs-scriptdocs": {
      "url": "https://scriptdocs-mcp.onrender.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-scriptmasterlabs-scriptdocs": {
      "type": "http",
      "url": "https://scriptdocs-mcp.onrender.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-scriptmasterlabs-scriptdocs]
url = "https://scriptdocs-mcp.onrender.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-scriptmasterlabs-scriptdocs": {
      "type": "remote",
      "url": "https://scriptdocs-mcp.onrender.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-scriptmasterlabs-scriptdocs --url 'https://scriptdocs-mcp.onrender.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-scriptmasterlabs-scriptdocs:
    url: "https://scriptdocs-mcp.onrender.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-scriptmasterlabs-scriptdocs": {
      "Transport": "http",
      "Url": "https://scriptdocs-mcp.onrender.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-scriptmasterlabs-scriptdocs -t streamable-http -u 'https://scriptdocs-mcp.onrender.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-scriptmasterlabs-scriptdocs": {
      "type": "http",
      "url": "https://scriptdocs-mcp.onrender.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-05 (score 73, +1)

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

### 2026-11-03 (score 72, +1)

- [security] Tool “docs_check_vulnerabilities” rewrote its description, which is the text the model reads
- [security] Tool “docs_get_readme” rewrote its description, which is the text the model reads

### 2026-11-01 (score 71, +1)

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

### 2026-10-30 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-29 (score 69)

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` (~426 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. [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.]

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` (~611 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 [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…

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: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-scriptmasterlabs-scriptdocs/scriptdocs-mcp#diagnostics

## Score history

- 2026-11-05: 73
- 2026-11-04: 72
- 2026-11-03: 72
- 2026-11-02: 71
- 2026-11-01: 71
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 69

## Common questions

### What is the SCRIPTMASTERLABS — ScriptDocs MCP server?

SCRIPTMASTERLABS — ScriptDocs is an MCP server listed in the public MCP registry as com.scriptmasterlabs/scriptdocs. Live npm/PyPI/crates facts + README fetch for agents. Settle-proven 2026-11-02 (SELF-PROOF). This page covers its hosted endpoint (https://scriptdocs-mcp.onrender.com/mcp).

### Is the SCRIPTMASTERLABS — ScriptDocs MCP server safe to use?

SCRIPTMASTERLABS — ScriptDocs scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the SCRIPTMASTERLABS — ScriptDocs MCP server expose?

SCRIPTMASTERLABS — ScriptDocs exposes 5 tools: docs_get_package_info, docs_get_readme, docs_search_docs, docs_check_vulnerabilities, docs_resolve_library. Their descriptions and schemas cost roughly 2,015 tokens of context every time the server is loaded.

### Does the SCRIPTMASTERLABS — ScriptDocs MCP server require authentication?

No. We connected to SCRIPTMASTERLABS — ScriptDocs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SCRIPTMASTERLABS — ScriptDocs MCP server still maintained?

SCRIPTMASTERLABS — ScriptDocs is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://scriptdocs-mcp.onrender.com/mcp
- Website: https://scriptmasterlabs.com/scriptdocs
- Changelog RSS feed: https://verifymcp.io/servers/com-scriptmasterlabs-scriptdocs/scriptdocs-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-scriptmasterlabs-scriptdocs/scriptdocs-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-scriptmasterlabs-scriptdocs/scriptdocs-mcp