memroam

MCPcommunitydegraded
v0.4.1UnknownMITUpdated 7d agonpm

Portable AI memory over a local folder or hosted vault, served via MCP — your memory roams with you across models and harnesses (Claude, ChatGPT, Codex, Cursor). Per-project spaces plus a shared layer, stored as plain markdown you own.

Endpoint healthdegraded
checked 3 days ago · never seen reachable
0% of the last 1 check reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). 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 →
488Downloads/wk
7d agoLast update
Package
AuthorUnknown
LicenseMIT
Version0.4.1
Sourcenpm+mcp-registry
Trust Status
B
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 surface9 tools · 2 privileged
Security scan✓ Cleanv0.4.1 · 4d agoHow well does this scan work?
CODEsrc/hosted/icon.mjsVery large base64-looking blob in source (in minified file)
EvalsNone
IndexedAug 27, 2026

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

Tools

9 tools · 2 privileged
Statically extracted from the published packagev0.4.1 · 4d 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.

memroamNo description published

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

viewView a file or directory in the memory folder. Directories list their entries; files return numbered lines. Start every session by viewing MEMORY.md, the index.

View a file or directory in the memory folder. Directories list their entries; files return numbered lines. Start every session by viewing MEMORY.md, the index.

No input schema was published for this tool.

searchSearch memories by keyword across the whole vault — frontmatter and body, all spaces. Returns matching files ranked by relevance with the first matching line. Use this to find memories when you don't know the path; view is for reading known paths.

Search memories by keyword across the whole vault — frontmatter and body, all spaces. Returns matching files ranked by relevance with the first matching line. Use this to find memories when you don't know the path; view is for reading known paths.

No input schema was published for this tool.

fetchFetch one memory file in full by its id — the vault-relative path that search results and MEMORY.md entries use (e.g. 'shared/some-memory.md'). Returns the complete contents.

Fetch one memory file in full by its id — the vault-relative path that search results and MEMORY.md entries use (e.g. 'shared/some-memory.md'). Returns the complete contents.

No input schema was published for this tool.

createCreate a file in the memory folder. Memories are markdown files with 'name:' and 'description:' frontmatter; MEMORY.md regenerates automatically — the description becomes the index line. Refuses to replace an existing file unless overwrite is true; to change an existing memory, edit it with str_rep…

Create a file in the memory folder. Memories are markdown files with 'name:' and 'description:' frontmatter; MEMORY.md regenerates automatically — the description becomes the index line. Refuses to replace an existing file unless overwrite is true; to change an existing memory, edit it with str_rep…

No input schema was published for this tool.

str_replaceReplace an exact string in a memory file. The old string must occur exactly once.

Replace an exact string in a memory file. The old string must occur exactly once.

No input schema was published for this tool.

insertInsert text after a given line in a memory file (0 = beginning of file).

Insert text after a given line in a memory file (0 = beginning of file).

No input schema was published for this tool.

deleteprivilegedDelete a file or directory in the memory folder. The MEMORY.md index updates automatically.

Delete a file or directory in the memory folder. The MEMORY.md index updates automatically.

No input schema was published for this tool.

renameprivilegedMove or rename a file or directory within the memory folder.

Move or rename a file or directory within the memory folder.

No input schema was published for this tool.

8 of 9 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

Portable AI memory over a local folder or hosted vault, served via MCP — your memory roams with you across models and harnesses (Claude, ChatGPT, Codex, Cursor). Per-project spaces plus a shared layer, stored as plain markdown you own.

Keywords
mcpmcp-servermemoryclaudeagent-memorymodel-context-protocolchatgptcodexcursorportable-memorycross-harnessai-memoryclaude-code
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-08-29 — observed resolution, not a publisher declaration.

0 packages resolved · 0 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

This package declares no runtime dependencies.

Topics

Related in memory & knowledge graphs