NPMScan

Get basic profile info for an npm maintainer

get_maintainer_profile

Read-only

Given an npm username, returns every package npm's own maintainer: search index currently returns for that account (registry.npmjs.org's /-/v1/search — the public registry API has no dedicated 'list packages by maintainer' endpoint otherwise), plus precomputed aggregates: currentlyMaintainsCount (still listed as maintainer right now vs. already-revoked), totalWeeklyDownloads and totalDependents summed across every returned package, and avatarUrl — a proxied Gravatar image (null if no email is on record). This is a plain info lookup — it does NOT run the publish-cluster / compromised-account detection that check_maintainer_blast_radius does; use that tool instead when the goal is a security read on whether this account's recent activity looks like a takeover, not just a profile summary. Natural pairing with check_maintainer_changes: once that tool names a maintainer on a package, call this with that maintainer's username to see the rest of what they touch. npmscanUrl is this account's profile page on npmscan itself; npmProfileUrl is the account's actual page on npmjs.com, included for verification since that's the authoritative record of the account.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	How many packages to list (default 50, max 250), most-downloaded first. Totals still cover every package found.
`maintainerUsername`	Yes	Exact npm username, e.g. "sindresorhus" — as shown at npmjs.com/~username. Not an email address, not a package name or scope.

Output Schema

TableJSON Schema

Name	Required	Description
`note`	Yes
`packages`	Yes
`avatarUrl`	Yes
`npmscanUrl`	Yes
`npmProfileUrl`	Yes
`packagesOmitted`	Yes	Packages left out of `packages` by `limit`; totals and scoring still include them.
`totalDependents`	Yes
`packagesReturned`	Yes
`resultsTruncated`	Yes
`maintainerUsername`	Yes
`totalPackagesFound`	Yes
`totalWeeklyDownloads`	Yes
`currentlyMaintainsCount`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 6, 2026

addedInput schema / properties / limit

Added value: +{
+  "description": "How many packages to list (default 50, max 250), most-downloaded first. Totals still cover every package found.",
+  "maximum": 250,
+  "minimum": 1,
+  "type": "integer"
+}

addedOutput schema / properties / packagesOmitted

Added value: +{
+  "description": "Packages left out of `packages` by `limit`; totals and scoring still include them.",
+  "type": "number"
+}

changedOutput schema / required

Previous value: -[
-  "maintainerUsername",
-  "npmscanUrl",
-  "npmProfileUrl",
-  "avatarUrl",
-  "totalPackagesFound",
-  "packagesReturned",
-  "resultsTruncated",
-  "currentlyMaintainsCount",
-  "totalWeeklyDownloads",
-  "totalDependents",
-  "packages",
-  "note"
-]New value: +[
+  "maintainerUsername",
+  "npmscanUrl",
+  "npmProfileUrl",
+  "avatarUrl",
+  "totalPackagesFound",
+  "packagesReturned",
+  "resultsTruncated",
+  "packagesOmitted",
+  "currentlyMaintainsCount",
+  "totalWeeklyDownloads",
+  "totalDependents",
+  "packages",
+  "note"
+]

Changed2 schema fields changedSep 8, 2026

addedOutput schema / properties / npmscanUrl
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "maintainerUsername",
-  "npmProfileUrl",
-  "avatarUrl",
-  "totalPackagesFound",
-  "packagesReturned",
-  "resultsTruncated",
-  "currentlyMaintainsCount",
-  "totalWeeklyDownloads",
-  "totalDependents",
-  "packages",
-  "note"
-]New value: +[
+  "maintainerUsername",
+  "npmscanUrl",
+  "npmProfileUrl",
+  "avatarUrl",
+  "totalPackagesFound",
+  "packagesReturned",
+  "resultsTruncated",
+  "currentlyMaintainsCount",
+  "totalWeeklyDownloads",
+  "totalDependents",
+  "packages",
+  "note"
+]

Changed2 schema fields changedSep 5, 2026

addedOutput schema / properties / avatarUrl

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

changedOutput schema / required

Previous value: -[
-  "maintainerUsername",
-  "npmProfileUrl",
-  "totalPackagesFound",
-  "packagesReturned",
-  "resultsTruncated",
-  "currentlyMaintainsCount",
-  "totalWeeklyDownloads",
-  "totalDependents",
-  "packages",
-  "note"
-]New value: +[
+  "maintainerUsername",
+  "npmProfileUrl",
+  "avatarUrl",
+  "totalPackagesFound",
+  "packagesReturned",
+  "resultsTruncated",
+  "currentlyMaintainsCount",
+  "totalWeeklyDownloads",
+  "totalDependents",
+  "packages",
+  "note"
+]

AddedSep 5, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already establish read-only/open-world safety, but the description adds substantive behavior: the reliance on an undocumented search index endpoint, that counts distinguish currently-maintained vs. revoked packages, that avatarUrl is a proxied Gravatar and can be null, and that npmProfileUrl is the authoritative record. This is context an agent could not get from annotations or schema.

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?

Dense but front-loaded, leading with the core behavior before the sibling disambiguation. Some clauses (e.g., the parenthetical about the missing registry endpoint) are lengthy, but each sentence carries distinct information rather than restating structured fields.

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?

Even though an output schema exists, the description proactively explains the aggregate fields and null behavior, and it covers scope, source, and sibling routing. Nothing needed to call the tool correctly is missing.

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 baseline is 3. The description adds value by explaining that limit affects only the returned list ('totals still cover every package found'), clarifying the interaction between the limit parameter and the reported aggregates.

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+resource ('given an npm username, returns every package...') plus the exact data source (the maintainer:<username> search index) and what aggregates come back. It explicitly differentiates itself from check_maintainer_blast_radius, so an agent can route correctly without opening schemas.

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?

Explicit when/when-not: it states it does NOT run the publish-cluster/compromised-account detection and names check_maintainer_blast_radius for security reads. It also describes a concrete workflow pairing with check_maintainer_changes, covering the main alternative.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?