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

looot

v1.0.0

Published

looot CLI: connect an AI agent to the looot catalog (discover, inspect, run, and get billed for external capabilities) from the command line.

Readme

looot

One CLI (and MCP server) that connects your AI agent to the looot catalog: discover a capability, inspect its exact input/output schema and price, run it, and get billed only for what actually completed. One balance, no per-provider subscriptions or separate API keys to manage.

Install

npm install -g looot

Try it without an account

looot search "find a work email"          # browse the public catalog, prices included
looot inspect <endpoint-id>

Sign in and connect your agent

looot login

Prints a link and a short code and opens your browser. On looot.ai, check that the code matches, choose what the token may do and how long it lasts, and approve. The CLI picks up the token by itself: you never copy a secret. It is saved to ~/.config/looot/config.json (only you can read it) and listed in Settings, Agent tokens, where you can revoke it. looot logout revokes it and deletes the file.

looot init

Detects Claude Code, Cursor, or Codex on your machine and offers to add the looot MCP server, referencing $LOOOT_TOKEN instead of writing the secret into their config. looot init --dry-run shows what it would write. looot mcp install --client <name> prints just the MCP config.

Everyday commands

looot search "verify an email address"     # find endpoints by what you want to do
looot inspect <endpoint-id>                # exact input/output schema and price before you run it
looot run <endpoint-id> --input '{"...": "..."}' --wait
looot balance                              # what's left in your workspace
looot runs list                            # recent runs, status, cost
looot doctor                               # is everything set up correctly

Every command supports --format json|human|jsonl. Piped or redirected output is JSON by default; on a terminal you get a short human-readable summary.

Full reference

looot help --all

Security

Your token is never passed as a command-line flag (it would land in shell history). Set it via looot login, or the LOOOT_TOKEN environment variable. Human-formatted output redacts secret-looking fields.

Docs

looot.ai/docs