NPMScan

Get npm package details

get_package

Read-only

Fetch npm registry metadata for a package: latest version, install scripts (preinstall/postinstall are a key risk signal), maintainers, license, recent version history, weekly downloads, GitHub stars, TypeScript support, days since last publish, a topPackagesRank (position among npm's ~100k most-downloaded packages, from npmscan's own periodically-refreshed snapshot — not live), and a downloadTrend (growing/stable/declining vs. ~3 months ago). Also checks the LATEST version against OSV.dev for known vulnerabilities — isLatestVersionVulnerable/highestSeverity give a direct safe/not-safe answer, and each finding includes severity, a summary, and the fixedVersion to upgrade to (use get_package_version or query_vulnerabilities to check a specific older version instead). Also returns popularityTier/maintenanceTier (deterministic rule-based labels, not model-generated) and a plain-language maintenanceSummary, plus a possibleTyposquatOf flag if the name is one typo away from a top-5,000 package while itself being obscure — read deprecated and maintenanceSummary before recommending a package, since a long gap since the last release can mean either a stable/finished package or a slowing one. Includes a link to the full npmscan.com analysis page.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	Exact npm package name, e.g. "lodash" or "@scope/name"

Output Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`license`	Yes
`distTags`	Yes
`homepage`	Yes
`keywords`	Yes
`createdAt`	Yes
`modifiedAt`	Yes
`npmscanUrl`	Yes
`repository`	Yes
`description`	Yes
`githubStars`	Yes
`maintainers`	Yes
`downloadTrend`	Yes
`latestVersion`	Yes
`popularityTier`	Yes
`recentVersions`	Yes
`hasBuiltInTypes`	Yes
`highestSeverity`	Yes
`maintenanceTier`	Yes
`topPackagesRank`	Yes
`vulnerabilities`	Yes
`weeklyDownloads`	Yes
`latestVersionInfo`	Yes
`maintenanceSummary`	Yes
`possibleTyposquatOf`	Yes
`daysSinceLastPublish`	Yes
`isLatestVersionVulnerable`	Yes

Schema Changelog

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

Changed4 schema fields changedSep 1, 2026

addedOutput schema / properties / highestSeverity

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

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

addedOutput schema / properties / vulnerabilities

Added value: +{
+  "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"
+}

changedOutput schema / required

Previous value: -[
-  "name",
-  "description",
-  "license",
-  "homepage",
-  "repository",
-  "keywords",
-  "maintainers",
-  "distTags",
-  "latestVersion",
-  "latestVersionInfo",
-  "recentVersions",
-  "createdAt",
-  "modifiedAt",
-  "npmscanUrl",
-  "weeklyDownloads",
-  "githubStars",
-  "hasBuiltInTypes",
-  "daysSinceLastPublish",
-  "popularityTier",
-  "maintenanceTier",
-  "maintenanceSummary",
-  "topPackagesRank",
-  "downloadTrend",
-  "possibleTyposquatOf"
-]New value: +[
+  "name",
+  "description",
+  "license",
+  "homepage",
+  "repository",
+  "keywords",
+  "maintainers",
+  "distTags",
+  "latestVersion",
+  "latestVersionInfo",
+  "recentVersions",
+  "createdAt",
+  "modifiedAt",
+  "npmscanUrl",
+  "weeklyDownloads",
+  "githubStars",
+  "hasBuiltInTypes",
+  "daysSinceLastPublish",
+  "popularityTier",
+  "maintenanceTier",
+  "maintenanceSummary",
+  "topPackagesRank",
+  "downloadTrend",
+  "possibleTyposquatOf",
+  "isLatestVersionVulnerable",
+  "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": {
+    "createdAt": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "daysSinceLastPublish": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "description": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "distTags": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "downloadTrend": {
+      "additionalProperties": false,
+      "properties": {
+        "changePercent": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "direction": {
+          "enum": [
+            "growing",
+            "stable",
+            "declining",
+            "unknown"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "direction",
+        "changePercent"
+      ],
+      "type": "object"
+    },
+    "githubStars": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "hasBuiltInTypes": {
+      "type": "boolean"
+    },
+    "homepage": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "keywords": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "latestVersion": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "latestVersionInfo": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "dependencies": {
+              "additionalProperties": {
+                "type": "string"
+              },
+              "type": "object"
+            },
+            "deprecated": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "scripts": {
+              "additionalProperties": {
+                "type": "string"
+              },
+              "type": "object"
+            },
+            "tarball": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "version": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "version",
+            "dependencies",
+            "scripts",
+            "deprecated",
+            "tarball"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "license": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "maintainers": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "email": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "maintenanceSummary": {
+      "type": "string"
+    },
+    "maintenanceTier": {
+      "enum": [
+        "active",
+        "aging",
+        "stale",
+        "unknown"
+      ],
+      "type": "string"
+    },
+    "modifiedAt": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "type": "string"
+    },
+    "npmscanUrl": {
+      "type": "string"
+    },
+    "popularityTier": {
+      "enum": [
+        "very-high",
+        "high",
+        "moderate",
+        "low",
+        "very-low",
+        "unknown"
+      ],
+      "type": "string"
+    },
+    "possibleTyposquatOf": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "rank": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "name",
+            "rank"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "recentVersions": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "publishedAt": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "version": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "version",
+          "publishedAt"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "repository": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "topPackagesRank": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "weeklyDownloads": {
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "name",
+    "description",
+    "license",
+    "homepage",
+    "repository",
+    "keywords",
+    "maintainers",
+    "distTags",
+    "latestVersion",
+    "latestVersionInfo",
+    "recentVersions",
+    "createdAt",
+    "modifiedAt",
+    "npmscanUrl",
+    "weeklyDownloads",
+    "githubStars",
+    "hasBuiltInTypes",
+    "daysSinceLastPublish",
+    "popularityTier",
+    "maintenanceTier",
+    "maintenanceSummary",
+    "topPackagesRank",
+    "downloadTrend",
+    "possibleTyposquatOf"
+  ],
+  "type": "object"
+}

First observedAug 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already indicate readOnly, openWorld, and non-destructive behavior, so the bar is lower, but the description adds significant behavioral context: topPackagesRank is from a periodically-refreshed snapshot and not live; popularityTier/maintenanceTier are deterministic rule-based labels, not model-generated; possibleTyposquatOf has a specific definition; and the vulnerability fields are described as giving a 'direct safe/not-safe answer.' No contradictions with annotations exist.

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 long, but nearly every clause adds decision-relevant information, such as install scripts being a key risk signal, snapshot staleness, and tier derivation. It is front-loaded with the core resource and risk signal, and the length is justified by the tool's rich output. It loses a point only for being dense and somewhat run-on.

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 tool with one parameter and a rich output schema, the description covers all the non-obvious semantics an agent needs: interpretability of downloadTrend, staleness of ranking data, how to interpret last-publish gaps, typosquatting detection, and where to find the full analysis page. The output schema already exists, so the description does not need to restate return types. Nothing critical 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% and the sole parameter, name, is already well-defined in the schema as an exact npm package name with examples. The tool description repeats that it fetches package metadata but adds no parameter semantics beyond the schema. Baseline 3 is appropriate because the schema carries the full burden.

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 opens with a specific verb and resource: 'Fetch npm registry metadata for a package' and enumerates concrete returned fields (latest version, install scripts, maintainers, license, downloads, vulnerability check). It also explicitly distinguishes itself from get_package_version by clarifying it checks the LATEST version against OSV.dev while older versions require a different tool.

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

Usage Guidelines5/5

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

The description gives explicit routing guidance: 'use get_package_version or query_vulnerabilities to check a specific older version instead.' It also instructs the agent to read deprecated and maintenanceSummary before recommending a package, and explains the interpretation nuance of long gaps since last publish. This clearly communicates when to use this tool versus alternatives.

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?