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

@moonarc/mcp

v0.1.0

Published

MCP server and CI CLI for Moonarc: search the catalogue by intent and byte budget, read a component's craft notes and source, get the install command; with a Pro key, audit motion in your codebase, measure per-route JS of your build, and compose sections.

Readme

@moonarc/mcp

MCP server for Moonarc. Local, stdio, no account.

claude mcp add moonarc -- npx -y @moonarc/mcp

Cursor, VS Code and Codex take the same command in their own config files: moonarc.dev/mcp has each one.

Tools: search_motion(intent, max_js_bytes?, tier?, limit?), get_component(name), get_install_command(names, method?), get_usage(). The catalogue is bundled at publish time. MOONARC_CATALOG_URL reads a catalogue of the same shape from a URL instead, a mirror or a test's; when that URL fails, takes over 5 s or answers another shape, the bundled copy answers.

Pro

With a Pro key in MOONARC_KEY, three more tools appear: audit_motion(paths, format?), measure_budget(dist, ceiling?, base?, format?) and compose_section(intent). The server asks Polar whether the key is valid and keeps a definite answer for the life of the process. Without a key and without MOONARC_CATALOG_URL, it makes no network request.

The client starts the server, and most clients pass it only a few of your environment variables, so put the key in the client's config:

  • Claude Code: claude mcp add --env MOONARC_KEY=<your key> --transport stdio moonarc -- npx -y @moonarc/mcp (keep an option between --env and the name, or the CLI reads the name as another variable)
  • Cursor, in .cursor/mcp.json: "env": { "MOONARC_KEY": "${env:MOONARC_KEY}" } beside command
  • VS Code, in .vscode/mcp.json: an input { "type": "promptString", "id": "moonarc-key", "password": true } and "env": { "MOONARC_KEY": "${input:moonarc-key}" }
  • Codex, in ~/.codex/config.toml: env_vars = ["MOONARC_KEY"] under [mcp_servers.moonarc]

get_usage tells you which plan the server validated.

The same package runs the audit and the byte meter as commands, for CI:

npx -y @moonarc/mcp audit src
npx -y @moonarc/mcp measure dist --ceiling 30000

audit exits 1 when it finds an error. measure reads the folder astro build wrote (a server build's dist/client is found by itself), takes --ceiling in raw bytes per page and --base when the site sets one, and exits 1 when a page is over the ceiling. Both exit 2 on a usage mistake, a refused key or a folder that is not a build.