pickfit

BrowseMCP servers

memnest

Local memory service that lets coding AIs save and look up past decisions from original text.

Tested on LinuxKnown vulnerabilities

Use it

Before you install: known vulnerabilities

pickfit found 2 known high or critical vulnerabilities in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.

  • crates:quinn-proto 0.11.15 Peer minimum ACK delay can panic quinn-proto when ACK_FREQUENCY transmission is enabled (RUSTSEC-2026-0340, high, fixed in 0.11.18)
See 1 more

Linux x86_64

You need first

  • Runtimes: Python 3 is needed for setup
  • At least 1.9 GB of RAM
  1. download memnest v0.4.3 release archive

    curl -fsSL https://github.com/Blue-B/memnest/releases/download/v0.4.3/memnest-v0.4.3-x86_64-unknown-linux-gnu.tar.gz -o /tmp/memnest.tar.gz
  2. extract archive and install memnest binary to ~/.local/bin

    mkdir -p /tmp/mn_extract && tar -xzf /tmp/memnest.tar.gz -C /tmp/mn_extract && mkdir -p ~/.local/bin && cp /tmp/mn_extract/memnest ~/.local/bin/memnest && chmod +x ~/.local/bin/memnest
Where the README and reality differ
  • README: memory_search(query="...")
    What worked: requires project or cwd; use project="all" for cross-project search e.g. {"query":"test","project":"all"}

Add it to your agent

claude mcp add memnest -- memnest --mcp
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "memnest": {
      "command": "memnest",
      "args": [
        "--mcp"
      ]
    }
  }
}

Add memnest as an MCP server in your coding AI's settings, then use its memory tools such as memory_search and memory_remember from your chat.

What it does

These come from the README; pickfit didn’t check them one by one.

  • Look up past decisions and the reasons behind them
    Not tested
  • Save important decisions on purpose
    Not tested
  • Share one memory across your coding AIs
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. A tool call works
  4. Works offline

macOS: the project says it runs there; pickfit hasn’t tried it.

Good for

  • Find the discussion behind switching task managers
  • Look up last settled deployment approach and why
  • Look up what was tried last time an error happened

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

An MCP client connects and lists its tools

  • Replayed from scratch
  • Works offline
  • Checked on 31 Oct 2026
  • Version 0.4.3

An MCP client handshake over stdio listed 5 tools.

Differences the test machine hit

  • README: curl -fsSL https://raw.githubusercontent.com/Blue-B/memnest/main/core/scripts/install.sh | bash installs and starts service
    In the test: install.sh requires systemd-analyze and systemd unit paths; in sandbox it fails with 'systemd-analyze: command not found'. Manually download tarball and copy memnest binary to ~/.local/bin works; run MCP via memnest --mcp
  • README: first write or search downloads 1.1GB embedding model
    In the test: first memory_search took ~18s to download model; subsequent offline calls succeed from cache

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.