NPMScan

Batch query known vulnerabilities

batch_query_vulnerabilities

Read-only

Query OSV.dev for known vulnerabilities across a whole npm dependency inventory at once: either pass a flat {packages:[...]} list, or paste raw package.json / lockfile / CycloneDX JSON / SPDX JSON content via content. The tool normalizes npm dependencies first, then chunk-queries OSV behind the scenes so large SBOMs don't stop at the upstream 100-package batch limit. Each finding includes severity, a summary, CVE aliases, and the fixed version — not just a bare advisory ID — so a dependency audit answer doesn't need a follow-up call per flagged package.

Input Schema

TableJSON Schema

Name	Required	Description
`content`	No	Raw dependency inventory content: package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, CycloneDX JSON, or SPDX JSON. Use this OR `packages`, not both.
`packages`	No	Explicit package list (1-1000 items). Use this OR `content`, not both.
`includeDevDependencies`	No	Ignored when using `packages`; only applies when `content` is a manifest/lockfile format that distinguishes dev dependencies.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	Yes
`warnings`	No
`inputFormat`	No
`ignoredCount`	No
`enrichmentNote`	No
`queryFailureCount`	No
`parsedPackageCount`	No
`totalVulnerabilities`	Yes
`packagesWithVulnerabilities`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed3 schema fields changedSep 1, 2026

changedInput schema / properties / content / description

Previous value: -"Optional raw dependency inventory content: package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, CycloneDX JSON, or SPDX JSON."New value: +"Raw dependency inventory content: package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, CycloneDX JSON, or SPDX JSON. Use this OR `packages`, not both."

changedInput schema / properties / includeDevDependencies / description

Previous value: -"Only applies when `content` is a package manifest/lockfile format that can distinguish dev dependencies. Default false."New value: +"Ignored when using `packages`; only applies when `content` is a manifest/lockfile format that distinguishes dev dependencies."

changedInput schema / properties / packages / description

Previous value: -"Optional explicit package list (1-1000 items). Use this OR `content`, not both."New value: +"Explicit package list (1-1000 items). Use this OR `content`, not both."

Changed10 schema fields changedSep 1, 2026

addedInput schema / properties / content

Added value: +{
+  "description": "Optional raw dependency inventory content: package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, CycloneDX JSON, or SPDX JSON.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / includeDevDependencies

Added value: +{
+  "description": "Only applies when `content` is a package manifest/lockfile format that can distinguish dev dependencies. Default false.",
+  "type": "boolean"
+}

changedInput schema / properties / packages / description

Previous value: -"1-100 packages to check"New value: +"Optional explicit package list (1-1000 items). Use this OR `content`, not both."

changedInput schema / properties / packages / maxItems
```
Previous value: -100New value: +1000
```
removedInput schema / required
```
Removed value: -[
-  "packages"
-]
```
addedOutput schema / properties / ignoredCount
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / inputFormat
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / parsedPackageCount
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / queryFailureCount
```
Added value: +{
+  "type": "number"
+}
```

addedOutput schema / properties / warnings

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed1 schema field changedSep 1, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "enrichmentNote": {
+      "type": "string"
+    },
+    "packagesWithVulnerabilities": {
+      "type": "number"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "npmscanUrl": {
+            "type": "string"
+          },
+          "package": {
+            "additionalProperties": false,
+            "properties": {
+              "name": {
+                "type": "string"
+              },
+              "version": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "name"
+            ],
+            "type": "object"
+          },
+          "vulnerabilities": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "aliases": {
+                  "items": {
+                    "type": "string"
+                  },
+                  "type": "array"
+                },
+                "fixedVersion": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "id": {
+                  "type": "string"
+                },
+                "npmscanUrl": {
+                  "type": "string"
+                },
+                "publishedAt": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "severity": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "summary": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                }
+              },
+              "required": [
+                "id",
+                "summary",
+                "severity",
+                "aliases",
+                "publishedAt",
+                "fixedVersion",
+                "npmscanUrl"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "vulnerabilityCount": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "package",
+          "npmscanUrl",
+          "vulnerabilityCount",
+          "vulnerabilities"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "totalVulnerabilities": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "results",
+    "totalVulnerabilities",
+    "packagesWithVulnerabilities"
+  ],
+  "type": "object"
+}

First observedAug 1, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses meaningful behavior: it normalizes npm dependencies first, chunk-queries OSV.dev behind the scenes, handles large inputs past the upstream 100-package limit, and returns enriched findings with severity, summary, CVE aliases, and fixed versions.

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

Conciseness4/5

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

The description is front-loaded and information-dense, covering purpose, input modes, internal behavior, and output value. It is slightly longer than strictly necessary because some format details are also present in the schema, but every sentence contributes useful decision-making context.

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?

Given the optional mutually exclusive parameters, the external OSV.dev dependency, and the batch behavior, the description covers the key aspects an agent needs: input options, normalization, chunking behavior, and what kind of findings are returned. The output schema handles return-value details, so the description is sufficiently complete.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds context about input formats and normalization, but most parameter meaning is already present in the schema. It does not materially enrich the semantics of `packages`, `content`, or `includeDevDependencies` beyond what the schema states.

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?

The description clearly states a specific verb and resource: querying OSV.dev for known vulnerabilities across a whole npm dependency inventory. It also distinguishes itself from per-package or single-CVE tools by emphasizing batch operation and that no follow-up call is needed per flagged package.

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?

The description gives clear context for when to use this tool: when auditing an entire npm dependency inventory at once, including large SBOMs. It implies the alternative of querying per package, but it does not explicitly name query_vulnerabilities or state when not to use it.

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

All NPMScan tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation4/5

Most tools have clearly distinct scopes, such as flat vs. transitive vulnerability checks and per-package vs. GitHub-repo audits. The main ambiguity is that several tools all ultimately report OSV/NVD findings or perform install-script risk checks, though the descriptions do draw clear boundaries and include cross-references to steer selection.

Naming Consistency5/5

Every tool follows a consistent lowercase snake_case verb_noun pattern, e.g. analyze_install_script, check_maintainer_changes, prioritize_remediation. The naming is predictable and makes the action and target of each tool immediately clear.

Tool Count3/5

At 22 tools, the surface is at the heavy end of the rubric and pushes beyond the typical 3-15 well-scoped range. The tools are individually purposeful and broad in coverage, but the count is high enough that an agent faces a large decision space and several workflows that overlap or compose in complex ways.

Completeness5/5

The set covers the full npm supply-chain assessment lifecycle: discovery, metadata lookup, vulnerability scanning, transitive dependency analysis, license checks, install-script analysis, maintainer and provenance checks, SBOM generation, dependency diffs, upgrade simulation, remediation prioritization, and alternative suggestion. There are no obvious dead ends or major missing operations for the stated domain.

Resources

Need Help?