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

@dev-vortex/pi-muninn-mcp

v0.1.0

Published

MCP server exposing @dev-vortex/pi-muninn memory/continuity tools to Claude Code.

Readme

@dev-vortex/pi-muninn-mcp

MCP server that gives Claude Code direct access to @dev-vortex/pi-muninn's project-memory and continuity tools — check status, write, and query project memory without going through a Pi session or an LLM round-trip.

Requirements

Install

Register it with Claude Code, either globally (applies to every project):

claude mcp add --scope user pi-muninn-mcp -- npx -y @dev-vortex/pi-muninn-mcp

or per-project, in that project's .mcp.json:

{
  "mcpServers": {
    "pi-muninn-mcp": { "command": "npx", "args": ["-y", "@dev-vortex/pi-muninn-mcp"] }
  }
}

Claude Code prompts to approve the server on first use either way.

Tools

| MCP tool | Purpose | |------------------------------|-------------------------------------------------------------| | pi_project_memory_status | Report whether project memory is enabled and its db state | | pi_project_memory_enable | Enable/disable project-scoped memory for a workspace | | pi_continuity_write | Persist a plan/decision/discovery/progress/outcome entry | | pi_continuity_query | Query stored continuity entries | | pi_memory_search | Semantic search across stored memories | | pi_memory_save | Explicitly save a fact/decision to persistent memory |

Every tool takes an optional projectRoot; when omitted it targets whatever project Claude Code currently has open.

Getting Claude to use these tools well

Tool descriptions alone cover per-call parameters, not judgment calls like "check status before starting work" or "write continuity as you go." This package ships a CLAUDE.md usage policy — copy it into your own project (or your global ~/.claude/CLAUDE.md) to cover exactly that.

License

MIT