NPMScan

Query known vulnerabilities for a package

query_vulnerabilities

Read-only

Query OSV.dev for known vulnerabilities affecting an npm package, optionally scoped to one exact version (e.g. to check whether a version pinned in a lockfile is safe). Returns isVulnerable and highestSeverity as a direct answer, plus each finding's severity, a plain-language summary, CVE aliases, and the fixedVersion to upgrade to — not a raw advisory dump. Use before recommending, installing, or upgrading a package.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	npm package name
`version`	No	Optional exact version to narrow results, e.g. to check one version pinned in a lockfile
`ecosystem`	No	OSV ecosystem, default "npm"

Output Schema

TableJSON Schema

Name	Required	Description	Default
`package`	Yes
`version`	Yes
`npmscanUrl`	Yes
`isVulnerable`	Yes
`highestSeverity`	Yes
`vulnerabilities`	Yes

Schema Changelog

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

Changed16 schema fields changedSep 1, 2026

changedInput schema / properties / version / description

Previous value: -"Optional exact version to narrow results"New value: +"Optional exact version to narrow results, e.g. to check one version pinned in a lockfile"

addedOutput schema / properties / highestSeverity

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / isVulnerable
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / version

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / properties / vulnerabilities / items / additionalProperties
```
Previous value: -trueNew value: +false
```
removedOutput schema / properties / vulnerabilities / items / properties / details
```
Removed value: -{
-  "type": "string"
-}
```
addedOutput schema / properties / vulnerabilities / items / properties / fixedVersion
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
removedOutput schema / properties / vulnerabilities / items / properties / modified
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / vulnerabilities / items / properties / published
```
Removed value: -{
-  "type": "string"
-}
```
addedOutput schema / properties / vulnerabilities / items / properties / publishedAt
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

removedOutput schema / properties / vulnerabilities / items / properties / references

Removed value: -{
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "type": {
-        "type": "string"
-      },
-      "url": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "url"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

removedOutput schema / properties / vulnerabilities / items / properties / severity / items

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "score": {
-      "type": "string"
-    },
-    "type": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "type",
-    "score"
-  ],
-  "type": "object"
-}

changedOutput schema / properties / vulnerabilities / items / properties / severity / type
```
Previous value: -"array"New value: +[
+  "string",
+  "null"
+]
```
changedOutput schema / properties / vulnerabilities / items / properties / summary / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / vulnerabilities / items / required

Previous value: -[
-  "id"
-]New value: +[
+  "id",
+  "summary",
+  "severity",
+  "aliases",
+  "publishedAt",
+  "fixedVersion",
+  "npmscanUrl"
+]

changedOutput schema / required

Previous value: -[
-  "package",
-  "npmscanUrl",
-  "vulnerabilities"
-]New value: +[
+  "package",
+  "version",
+  "npmscanUrl",
+  "isVulnerable",
+  "highestSeverity",
+  "vulnerabilities"
+]

Changed1 schema field changedSep 1, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "npmscanUrl": {
+      "type": "string"
+    },
+    "package": {
+      "type": "string"
+    },
+    "vulnerabilities": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "aliases": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "details": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "modified": {
+            "type": "string"
+          },
+          "npmscanUrl": {
+            "type": "string"
+          },
+          "published": {
+            "type": "string"
+          },
+          "references": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "type": {
+                  "type": "string"
+                },
+                "url": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "url"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "severity": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "score": {
+                  "type": "string"
+                },
+                "type": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "type",
+                "score"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "summary": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "package",
+    "npmscanUrl",
+    "vulnerabilities"
+  ],
+  "type": "object"
+}

First observedAug 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already mark it read-only and non-destructive; the description adds useful behavioral context beyond annotations by specifying it returns a summarized 'direct answer' and 'not a raw advisory dump,' while noting the external source (OSV.dev). No contradiction with the readOnlyHint.

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

Conciseness5/5

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

Three tight sentences cover purpose, return shape, and usage timing. The most decision-relevant information is front-loaded with no filler or repetition of schema details.

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?

For a simple 3-parameter read-only tool with 100% schema coverage and an output schema, the description fully covers what the tool does, what it returns, and when to use it. Nothing an agent needs to select and invoke it correctly is missing.

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 reinforces the version parameter's purpose via the lockfile example, but it does not add new meaning beyond what the input schema already provides.

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 ('Query OSV.dev for known vulnerabilities affecting an npm package') with an optional exact-version scope. This clearly distinguishes it from siblings by promising a direct isVulnerable answer for a single package, not a raw advisory feed.

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?

Explicitly directs use 'before recommending, installing, or upgrading a package,' giving clear decision context. It does not explicitly name when-not-to-use or alternatives such as batch_query_vulnerabilities, so it falls just short of a 5.

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?