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

@mnemodb/mcp

v0.1.11

Published

MnemoDB memory engine as an MCP server: memory_recall, memory_remember, memory_review, memory_compact over human-readable .mem.md stores.

Readme

@mnemodb/mcp

The MnemoDB memory engine as an MCP server. Gives any MCP client — Claude Code, Cursor, Windsurf, Claude Desktop — persistent memory stored in human-readable, git-diffable .mem.md files.

claude mcp add mnemodb -- npx -y @mnemodb/[email protected]

Why this and not built-in memory

CLAUDE.md and Claude's memory tool already give agents memory. MnemoDB isn't a replacement — it's the structure they don't provide: typed entries with lifecycle (TTL, supersession, compaction), provenance and a trust model (tool-sourced memories are flagged untrusted and can't override human instructions), portability across tools, and auditable Markdown files you can git diff. Worth it when the agent maintains memory itself over many sessions, or you work across more than one tool. Full rationale: https://github.com/mnemodb/mnemodb

Tools

Eleven memory-semantic operations — things a plain memory folder can't do:

  • memory_boot — always-loaded context (preambles + pinned entries); call at session start
  • memory_list — list the whole store (no query needed); browse everything
  • memory_recall — ranked retrieval for a query, with provenance + untrusted flag
  • memory_show — one entry in full: body, all metadata, lifecycle status
  • memory_history — an entry's supersession lineage (what it replaced / what replaced it)
  • memory_stats — the store's self-report: counts by type/scope/provenance, budget, staleness
  • memory_remember — store a typed entry (dedup, provenance stamping, supersession)
  • memory_forget — auditable soft-delete to the archive (recoverable; trust-gated)
  • memory_pin — set an entry's load tier (always/auto/cold); guards against pinning untrusted content
  • memory_review — stale entries, contradictions, budget status
  • memory_compact — the vacuum pass (dry-run by default)

Setup — Claude Code

claude mcp add mnemodb -- npx -y @mnemodb/[email protected]

Or in .mcp.json at your project root:

{
  "mcpServers": {
    "mnemodb": { "command": "npx", "args": ["-y", "@mnemodb/[email protected]"] }
  }
}

The store is discovered at ./.memory (create one with npx @mnemodb/cli init), or set MNEMO_STORE=/path/to/store. Then add a short instruction to CLAUDE.md telling the agent to call memory_recall / memory_remember — see https://github.com/mnemodb/mnemodb/blob/main/docs/USAGE.md

Security stance

Everything written through memory_remember is stamped src: agent. Tool-derived content is data, never instructions (spec §10), flagged untrusted on recall so consuming agents don't obey it.