Mmcp.market

Polypack Memory MCP server

by imattau·io.github.imattau/polypack-mcp·v0.1.31

MCP server exposing Polypack as persistent adaptive memory

A92/100grade A
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

0 stars174 downloads/wk

Reviews

Write one

Nobody has reviewed Polypack Memory yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Polypack Memory tools (18, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • graph_query

    Inspect graph neighbors/schema or perform an advanced edge operation.

  • memory_consolidate

    Consolidate source memories into one durable higher-level memory.

  • memory_context

    Return a working-memory set selected by activation and estimated-token budget.

  • memory_deletewrite action

    Permanently delete one memory and its graph edges.

  • memory_feedback

    Record whether a retrieved memory helped this task.

  • memory_get

    Fetch one memory by exact ID, including its current state and revision.

  • memory_link

    Connect two memories with an explicit graph relationship.

  • memory_link_batch

    Connect multiple pairs of memories with explicit graph relationships in a single batch.

  • memory_list_contexts

    List context namespaces and the number of memories in each.

  • memory_recall

    Search memories by text, context, activation, and confidence.

  • memory_store

    Store durable project memory.

  • memory_store_batch

    Store multiple durable project memories in a single batch.

  • memory_store_with_link

    Store a new memory and link it to an existing memory in one call.

  • memory_supersede

    Replace an outdated fact while retaining its history.

  • memory_suppress

    Inhibit a stale or unhelpful memory without deleting it.

  • memory_thread

    Walk the RESPONDS_TO chain from a starting memory ID and return the thread.

  • memory_unlinkwrite action

    Remove graph edges between two memories.

  • memory_updatewrite action

    Update mutable memory fields without changing its content.

Public scan report

scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it

no findings
  • Code scan8 source files scanned25/25
  • Live reliabilityno gateway calls yet and no remote to proben/a
  • Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 14 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Install directly

claude mcp add polypack-mcp -- uvx polypack-mcp
Add to Cursor

Polypack Memory: common questions

Is Polypack Memory MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Polypack Memory safety report
How do I install Polypack Memory?
It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does Polypack Memory need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Polypack Memory maintained?
The last commit was 15 days ago (2026-09-06). The latest release is v0.1.31.
What can I use instead of Polypack Memory?
Servers from other publishers that do the same job: State Memory MCP server, Knowl MCP server and Hypermnesia MCP server. Compare all Polypack Memory alternatives.

Alternatives to Polypack Memory

Same job from other publishers: the closest match first, then the best rated.

All Polypack Memory alternatives →
  • State Memory MCP
    Deterministic, persistent graph server for tracking workflow state, decisions, and blockers.
    A
  • Knowl
    Persistent memory for Claude Code, Cursor and Codex. Facts retire when they change.
    A
  • Hypermnesia
    Persistent memory for AI agents — 36 cited neuroscience mechanisms, local-first, hybrid retrieval.
    A

More from imattau