`npm_package_stats`

Pack: jsdelivr · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/npm_package_stats for the schema, then POST the same URL with its arguments for the data.

Request counts + bandwidth for an npm package served via JSDelivr.

Parameters

Name	Type	Required	Description
`package_name`	string	yes	npm package name (scoped allowed)
`period`	string	no	day \| week \| month \| quarter \| year \| s-month \| s-quarter \| s-year (default month)

Example call

Arguments

{
  "package_name": "react"
}

curl

curl -X POST https://gateway.pipeworx.io/jsdelivr/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"npm_package_stats","arguments":{"package_name":"react"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('npm_package_stats', {
  "package_name": "react"
});

More examples

{
  "package_name": "@babel/core",
  "period": "week"
}

Response shape

Full JSON Schema

{
  "type": "object",
  "description": "JSDelivr stats for npm package (requests and bandwidth)"
}

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}

Connect to just the jsdelivr pack

{
  "mcpServers": {
    "jsdelivr": {
      "url": "https://gateway.pipeworx.io/jsdelivr/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

npm_package_stats