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

@bitflower/va-mcp

v1.0.2

Published

Install the Virtual Architect MCP server and SessionStart playbook into a Claude Code project.

Readme

@bitflower/va-mcp

Install the Virtual Architect MCP server and its SessionStart playbook into a Claude Code project, with a single command. The installer registers the virtual-architect MCP server with your local claude CLI and drops a SessionStart hook into the project so every Claude Code session in that directory can call Virtual Architect tools and starts with a short usage playbook in context. It runs entirely on your machine and makes no network call to discover or download anything at install time.

Install

npx @bitflower/va-mcp install \
    --url https://va.example.com/mcp \
    --api-key va_live_<your-key>

Targets the current directory by default; pass --project-dir <path> to target another project. Run install with no flags to be prompted interactively (the API key is masked as you type).

For reproducible installs (CI, shared setup scripts), pin a version:

npx @bitflower/[email protected] install --url <url> --api-key <key>

Uninstall

npx @bitflower/va-mcp uninstall

Deregisters the MCP server and removes the SessionStart hook entry. The hook script file is left on disk for you to delete manually.

Help and version

npx @bitflower/va-mcp --help
npx @bitflower/va-mcp --version

Requirements

gitignore precondition

If the target directory is a git repository, add .claude/settings.local.json to your .gitignore before running the installer — it refuses otherwise, so per-machine hook configuration never gets committed:

grep -qxF '.claude/settings.local.json' .gitignore || echo '.claude/settings.local.json' >> .gitignore

The check is deliberately conservative: it recognizes only an exact-path or directory-prefix entry — glob patterns (e.g. .claude/*), !-negation lines, and nested .gitignore files are not evaluated. The check is skipped for non-git directories. In a monorepo, put the entry in the project-local .gitignore (the one in the target directory), not the repo-root .gitignore — the installer reads only the target directory's file.

No catalog lookup or remote calls at install time

The installer performs no catalog lookup or remote download. It talks only to your local claude CLI and writes into the target project, so it works without outbound network access (beyond npx fetching the package itself).

Notes

  • Idempotent: re-running install with the same arguments produces the same on-disk state and does not duplicate the hook entry.
  • Windows: use WSL. A native Windows hook format is not part of this release.
  • Bearer token: your API key is passed only to the claude CLI and is never written to any file the installer creates.
  • Full setup guide: in-depth prerequisites, data-flow and bearer-exposure warnings, verification, key rotation, and LAN access are documented for Virtual Architect users as part of the platform docs.