Skip to main content
Glama

SCRIPTMASTERLABS — ScriptDocs

Check Package Vulnerabilities

docs_check_vulnerabilities
Read-onlyIdempotent

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ecosystem": "<ecosystem>",
      "package_name": "<package_name>"
    },
    "name": "docs_check_vulnerabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNoSpecific version to check. Defaults to the current latest published version if omitted.
ecosystemYesWhich package registry the version belongs to: 'npm', 'pypi', or 'cargo'.
package_nameYesExact package name as published on the registry.
include_fix_docsNoWhen 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world), and the description adds real value beyond them: it discloses that the tool never estimates risk, that README fetch failures degrade gracefully to recommended_fix=null without withholding vulnerability data, and it documents the x402 payment requirement and pricing across five chains. That payment/auth detail is exactly the kind of context annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with Args, Returns, and Error Handling sections, but the opening is padded with redundant framing ('here's what's wrong AND here's exactly what upgrading looks like' restates the same point twice). The payment block is necessary but dense enough to weigh down readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description enumerates every returned field (vulnerability_count, vulnerabilities with nested keys, recommended_fix, source_url, fetched_at) and covers error modes and partial-failure semantics. An agent has everything needed to call it and interpret the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning: it explains that version defaults to the latest published version and that include_fix_docs controls an extra README fetch whose failure is non-fatal. It also enumerates the ecosystem values, though that duplicates the schema enum.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Check a real, specific package version against OSV.dev') plus a secondary behavior (fetching the fixed version's README). It is unmistakably distinct from the docs_* siblings, which retrieve package info, READMEs, or docs rather than advisory data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for use and an explicit when-not: it names the tool as more limited than dedicated vulnerability-intelligence tools like VulnCheck and Snyk, which report exploit activity. It also clarifies that a zero-vulnerability result is valid rather than a failure. It stops short of naming which sibling to call instead for related-but-different needs such as plain package metadata.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources