npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

pipeworx

v0.2.0

Published

Call live data tools from your shell, or connect them to any AI agent

Readme

pipeworx

Call live data tools from your shell — job postings, SEC filings, weather, drug labels, court opinions, prediction markets — and get JSON back. No account, no API key, no MCP client.

npx pipeworx@latest call adzuna_search --country=us --what="solutions engineer" | jq .count

Or connect the same catalog to an AI agent as an MCP server. Both work; use whichever fits.

From a shell

Find a tool:

npx pipeworx@latest tools --grep "job postings"

Every name it prints is callable as-is. This matters: a pack's internal name is not always the name the gateway accepts — Adzuna publishes its search tool as search, but since that collides across packs the gateway exposes it as adzuna_search. pipeworx tools prints the name that works.

Call it:

# Flags — numbers and booleans are coerced
npx pipeworx@latest call adzuna_search --country=us --what=engineer --results_per_page=5

# Or JSON, for values that must stay strings (zip codes, IDs with leading zeros)
npx pipeworx@latest call adzuna_search --json '{"country":"us","what":"engineer"}'

# Ask in plain language and let the router pick the tool
npx pipeworx@latest call ask_pipeworx --question="What is the US trade deficit with China?"

It composes. The tool's JSON goes to stdout; everything else goes to stderr; a tool error exits non-zero.

npx pipeworx@latest call adzuna_search --country=us --what=nurse | jq -r '.results[].title'

if ! npx pipeworx@latest call adzuna_search --country=us --what=nurse > jobs.json; then
  echo "lookup failed" >&2; exit 1
fi

Options for call

| Flag | Meaning | |---|---| | --key=value | One tool argument; numbers and booleans coerced | | --json '<object>' | All arguments as JSON; individual flags override it | | --pack <slug> | Call a pack's own endpoint instead of the router | | --api-key <key> | Send a key (or set PIPEWORX_API_KEY) | | --timeout <secs> | Client timeout, default 90 |

As an MCP server

npx pipeworx@latest install      # register with Claude Code
npx pipeworx@latest search weather
npx pipeworx@latest info weather
npx pipeworx@latest use weather  # launch claude with a pack loaded

Run npx pipeworx@latest help for the full command list.

Authentication

Anonymous calls are rate-limited by IP. A free key from pipeworx.io/account raises that:

export PIPEWORX_API_KEY=your_key_here

The CLI does not write your key to disk — set it in your environment like any other credential.

No Node.js?

Every command here is one HTTP POST. See the raw JSON-RPC guide for the curl equivalents.

Links

MIT