SCRIPTMASTERLABS — ScriptDocs MCP server
com.scriptmasterlabs/scriptdocsscriptmasterlabs.comstreamable-httpv1.0.2Scanned
Live npm/PyPI/crates facts + README fetch for agents. Settle-proven 2026-11-02 (SELF-PROOF).
5 tools: 1 change things and 4 only read.
- Reads private data · 4
- Reads text others write · 5
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the SCRIPTMASTERLABS — ScriptDocs MCP server can do
The SCRIPTMASTERLABS — ScriptDocs MCP server is published by scriptmasterlabs.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (1 tool: docs_check_vulnerabilities), but cannot delete data. 4 tools only read.
4 tools read private data (docs_get_package_info, docs_get_readme, docs_search_docs and 1 more); 5 tools bring in text other people can write (docs_get_package_info, docs_get_readme, docs_search_docs and 2 more).
The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 18, 2026, version 1.0.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 1Claude Code: ask
docs_check_vulnerabilitiesCheck 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'…Reads text others write1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description is 2,123 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...Xahau XAH (drops at the live XAH/USD rate). The other ScriptDocs tools are free.]"
Description, as the server wrote it 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.]
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 4Show 4 read-only tools
docs_get_package_infoFetch real, current metadata for a package directly from the npm registry, PyPI JSON API, or crates.io.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "docs_get_package_info" says "get": a word for reading.
What it can reach
- private-dataThe name "docs_get_package_info" says "get" and "doc": it reads documents.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
docs_get_readmeFetch the real README/description for a package, straight from the registry — not a summary, not a paraphrase, not AI-generated.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "docs_get_readme" says "get": a word for reading.
What it can reach
- private-dataThe name "docs_get_readme" says "get" and "doc": it reads documents.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.]
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
docs_resolve_libraryTurn 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.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "docs_resolve_library" says "resolve": a word for reading.
What it can reach
- private-dataThe name "docs_resolve_library" says "resolve" and "doc": it reads documents.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
docs_search_docsSearch for keywords inside a package's real README/docs and return verbatim matching snippets with surrounding context.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "docs_search_docs" says "search": a word for reading.
What it can reach
- private-dataThe name "docs_search_docs" says "search" and "doc": it reads documents.
- private-dataThe description's first sentence says "search" and "doc": it reads documents.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data4
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write5
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:23 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://scriptdocs-mcp.onrender.com/mcp: tools/list returned 5 tools to an anonymous client, including docs_check_vulnerabilities (write)
Findings
Matches of fixed checks, with the text they matched.
The description is 2,123 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...Xahau XAH (drops at the live XAH/USD rate). The other ScriptDocs tools are free.]"
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:docs_check_vulnerabilitiesChanges thingsdescription
- Changed:docs_get_readmeOnly readsdescription
Install
Pinned to version 1.0.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http scriptdocs https://scriptdocs-mcp.onrender.com/mcpclaude mcp add --transport http scriptdocs https://scriptdocs-mcp.onrender.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__scriptdocs__docs_get_package_info",
"mcp__scriptdocs__docs_get_readme",
"mcp__scriptdocs__docs_search_docs",
"mcp__scriptdocs__docs_resolve_library"
],
"ask": [
"mcp__scriptdocs__docs_check_vulnerabilities"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as scriptdocs. Review it before you use it.
Capability tags behind 5 rules
- mcp__scriptdocs__docs_get_package_info private-data, untrusted-input
- mcp__scriptdocs__docs_get_readme private-data, untrusted-input
- mcp__scriptdocs__docs_search_docs private-data, untrusted-input
- mcp__scriptdocs__docs_check_vulnerabilities untrusted-input
- mcp__scriptdocs__docs_resolve_library private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.scriptmasterlabs/scriptdocs/verify?hash=21b7d55dc5f5f653797add23b04fc81b43df71d399a09cbf51d0f220263458bc" | jq -e '.changed == false'Pinned hash 21b7d55dc5f5, from Nov 18, 2026, 20:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.scriptmasterlabs/scriptdocs/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.scriptmasterlabs/scriptdocs)Source: MCP Registry. Synced Nov 5, 2026, 02:17 UTC.
SCRIPTMASTERLABS — ScriptDocs MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the SCRIPTMASTERLABS — ScriptDocs MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the SCRIPTMASTERLABS — ScriptDocs MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the SCRIPTMASTERLABS — ScriptDocs MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the SCRIPTMASTERLABS — ScriptDocs MCP server have?
- 5 tools: 1 write, 4 read. docs_check_vulnerabilities, docs_get_package_info, docs_get_readme, docs_search_docs and docs_resolve_library.
Does the SCRIPTMASTERLABS — ScriptDocs MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the SCRIPTMASTERLABS — ScriptDocs MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the SCRIPTMASTERLABS — ScriptDocs MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 5, 2026. Every change is on this page and in its Atom feed.