An MCP server that gives LLMs persistent, searchable semantic memory
An MCP server that gives LLMs persistent, searchable semantic memory. ------|-------------| | Persist text + optional namespace/tags/metadata | | Semantic search (cosine similarity) over all memories | | Retrieve a single memory by ID | | Delete a memory by ID | | List memories with optional namespace/tag filter + pagination | | Count of memories, namespaces, DB path | | Update an existing memory…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
An MCP server that gives LLMs persistent, searchable semantic memory. ------|-------------| | Persist text + optional namespace/tags/metadata | | Semantic search (cosine similarity) over all memories | | Retrieve a single memory by ID | | Delete a memory by ID | | List memories with optional namespace/tag filter + pagination | | Count of memories, namespaces, DB path | | Update an existing memory | The server supports multiple embedding backends: TF-IDF (default): Pure Python, no external…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.