`get_package`

Pack: ecosystems · 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/get_package for the schema, then POST the same URL with its arguments for the data.

Get a package’s open metadata from ecosyste.ms — description, homepage, repository, license, latest version, monthly downloads, and dependent/usage counts. Works across 100+ registries. Keyless.

Parameters

Name	Type	Required	Description
`name`	string	yes	Package name, e.g. “react”, “@vue/cli”, “django”. Scopes/slashes are handled automatically.
`registry`	string	no	Registry name (default “npmjs.org”). e.g. “pypi.org”, “crates.io”, “rubygems.org”, “nuget.org”. Use list_registries to discover names.

Example call

Arguments

{
  "name": "lodash"
}

curl

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

TypeScript (@pipeworx/sdk)

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

const result = await pipeworx.call('get_package', {
  "name": "lodash"
});

More examples

{
  "name": "django",
  "registry": "pypi.org"
}

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 ecosystems pack

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

See Getting Started for client-specific install steps.

get_package