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

wall-mcp

v0.1.1

Published

A wall of complete landing pages to compare, choose from, and hand back to your agent as a spec. Runs on the Claude you already have.

Readme

Wall

Choose the feeling you like.

npm MCP Node License

Generating a page is solved. What nobody gives you is many at once, live, side by side — which is how design decisions are actually made. Wall's one act is compare and choose.

From your agent

One line, nothing else to install:

claude mcp add --scope user wall -- npx -y wall-mcp

Ask for a landing page. Wall opens in your browser, you browse a wall of real pages, pick one, and the choice returns to your project as a spec your agent implements in your own stack — design tokens, structure, and copy, not a static file to port.

Nothing else to download: npx resolves the latest version on every run, so Windows and Linux work without a build and a run is never stale. A desktop app is coming.

Three tools: design opens Wall and waits · collect reads a choice made after it stopped waiting · check names the patterns that make a page look generated.

From a clone

npm install
npm run web     # browser — the same code the MCP server opens
npm run serve   # self-hosted; ANTHROPIC_API_KEY stays on the server
npm run app     # the desktop shell, not released yet

Model keys are optional. Layouts, variants, and export all run locally with no key; a key is used only for model-written copy, and it never leaves your machine.

What it does

  • Forge twelve — six layout archetypes × your taste sheet, rendered as live pages, not screenshots. Instant, local, no template gallery.
  • Taste from a screenshot — drop a page you love and Wall reads the design system out of it into an editable contract.
  • Breed, don't prompt — pin two variants and the child takes one's layout and the other's typography.
  • Ship a real file — a self-contained index.html you own: inlined CSS, no framework, no runtime of ours.

Docs

Verify everything with npm run verify:all — real browsers, recorded streams, no key and no tokens spent.

MIT © Amin Khorramii