mneme-memory

Name: mneme-memory
Author: io.github.modusensus

MCPcommunity

v0.1.1io.github.modusensusMITUpdated 11d agonpm GitHub

Cross-session memory for AI coding agents via six tools; local-first SQLite store.

Works in

ClaudeCursorCopilotGemini

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.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

120GitHub stars

16Forks

11d agoLast update

Package

Authorio.github.modusensus

LicenseMIT

Version0.1.1

Sourcenpm+mcp-registry

npmmneme-memory

GitHubslow-stack/mneme

SBOMCycloneDX 1.6 ↓

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 0 resolved · none vulnerable

Tool surface6 tools · 1 privileged

Security scan✓ Cleanv0.1.1 · 10d agoHow well does this scan work?

EvalsNone

IndexedSep 24, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

6 tools · 1 privileged

Statically extracted from the published packagev0.1.1 · 10d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

memory_saveNo description published

This tool published no description. Forge does not invent one.

memory_searchauto (default) = keyword hits first + vector fill when enabled; keyword = text only; vector = semantic recall first (falls back to keyword); hybrid = vector leads, keyword fills remaining slots

auto (default) = keyword hits first + vector fill when enabled; keyword = text only; vector = semantic recall first (falls back to keyword); hybrid = vector leads, keyword fills remaining slots

No input schema was published for this tool.

memory_listFilter by type; omit for all. 'document' (#230) = agent-registered document pointer rows

Filter by type; omit for all. 'document' (#230) = agent-registered document pointer rows

No input schema was published for this tool.

memory_getNo description published

This tool published no description. Forge does not invent one.

memory_updateNo description published

This tool published no description. Forge does not invent one.

memory_deleteprivilegedNo description published

This tool published no description. Forge does not invent one.

2 of 6 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Cross-session memory for AI coding agents via six tools; local-first SQLite store.

Keywords

mcp

Alternatives

Comparing tool surfaces…

mneme-memory

Tools

Tools exposed

Dependency tree

Topics

Related in memory & knowledge graphs